NextEra Energy Capabilities

Naftiko 0.5 capability definitions for NextEra Energy - 100 capabilities showing integration workflows and service orchestrations.

Sort

Expand

Alteryx Workflow Execution ▼

analytics alteryx data-processing

Triggers an Alteryx analytics workflow and returns the execution status.

naftiko: "0.5"
info:
  label: "Alteryx Workflow Execution"
  description: "Triggers an Alteryx analytics workflow and returns the execution status."
  tags:
    - analytics
    - alteryx
    - data-processing
capability:
  exposes:
    - type: mcp
      namespace: analytics-workflows
      port: 8080
      tools:
        - name: run-alteryx-workflow
          description: "Trigger an Alteryx workflow by ID."
          inputParameters:
            - name: workflow_id
              in: body
              type: string
              description: "The Alteryx workflow identifier."
          call: "alteryx.run-workflow"
          with:
            workflow_id: "{{workflow_id}}"
          outputParameters:
            - name: job_id
              type: string
              mapping: "$.id"
            - name: status
              type: string
              mapping: "$.status"
  consumes:
    - type: http
      namespace: alteryx
      baseUri: "https://nextera.alteryxcloud.com/api/v3"
      authentication:
        type: bearer
        token: "$secrets.alteryx_token"
      resources:
        - name: workflows
          path: "/workflows/{{workflow_id}}/jobs"
          inputParameters:
            - name: workflow_id
              in: path
          operations:
            - name: run-workflow
              method: POST

Amazon Neptune Graph Query ▼

data-engineering amazon-neptune graph-database

Executes a graph query against Amazon Neptune for asset relationship mapping in the NextEra grid topology.

naftiko: "0.5"
info:
  label: "Amazon Neptune Graph Query"
  description: "Executes a graph query against Amazon Neptune for asset relationship mapping in the NextEra grid topology."
  tags:
    - data-engineering
    - amazon-neptune
    - graph-database
capability:
  exposes:
    - type: mcp
      namespace: graph-analytics
      port: 8080
      tools:
        - name: query-asset-graph
          description: "Run a Gremlin query on the asset graph in Amazon Neptune."
          inputParameters:
            - name: gremlin_query
              in: body
              type: string
              description: "The Gremlin traversal query."
          call: "neptune.execute-gremlin"
          with:
            query: "{{gremlin_query}}"
          outputParameters:
            - name: results
              type: array
              mapping: "$.result.data"
  consumes:
    - type: http
      namespace: neptune
      baseUri: "https://nextera-neptune.us-east-1.neptune.amazonaws.com:8182"
      authentication:
        type: aws
        accessKeyId: "$secrets.aws_access_key"
        secretAccessKey: "$secrets.aws_secret_key"
      resources:
        - name: gremlin
          path: "/gremlin"
          operations:
            - name: execute-gremlin
              method: POST

AWS Lambda Function Invocation ▼

cloud aws-lambda serverless

Invokes an AWS Lambda function and returns the execution result.

naftiko: "0.5"
info:
  label: "AWS Lambda Function Invocation"
  description: "Invokes an AWS Lambda function and returns the execution result."
  tags:
    - cloud
    - aws-lambda
    - serverless
capability:
  exposes:
    - type: mcp
      namespace: serverless
      port: 8080
      tools:
        - name: invoke-lambda
          description: "Invoke an AWS Lambda function by name."
          inputParameters:
            - name: function_name
              in: body
              type: string
              description: "The Lambda function name."
            - name: payload
              in: body
              type: string
              description: "JSON payload."
          call: "lambda.invoke-function"
          with:
            function_name: "{{function_name}}"
            payload: "{{payload}}"
          outputParameters:
            - name: status_code
              type: string
              mapping: "$.StatusCode"
            - name: result
              type: string
              mapping: "$.Payload"
  consumes:
    - type: http
      namespace: lambda
      baseUri: "https://lambda.us-east-1.amazonaws.com/2015-03-31"
      authentication:
        type: aws
        accessKeyId: "$secrets.aws_access_key"
        secretAccessKey: "$secrets.aws_secret_key"
      resources:
        - name: functions
          path: "/functions/{{function_name}}/invocations"
          inputParameters:
            - name: function_name
              in: path
          operations:
            - name: invoke-function
              method: POST

Azure Data Factory Pipeline Status ▼

data-engineering azure-data-factory

Checks the status of an Azure Data Factory pipeline run, returning run status, start time, and duration.

naftiko: "0.5"
info:
  label: "Azure Data Factory Pipeline Status"
  description: "Checks the status of an Azure Data Factory pipeline run, returning run status, start time, and duration."
  tags:
    - data-engineering
    - azure-data-factory
capability:
  exposes:
    - type: mcp
      namespace: data-engineering
      port: 8080
      tools:
        - name: get-adf-pipeline-status
          description: "Check Azure Data Factory pipeline run status by run ID."
          inputParameters:
            - name: run_id
              in: body
              type: string
              description: "The pipeline run identifier."
          call: "adf.get-pipeline-run"
          with:
            run_id: "{{run_id}}"
          outputParameters:
            - name: status
              type: string
              mapping: "$.status"
            - name: run_start
              type: string
              mapping: "$.runStart"
            - name: duration_ms
              type: string
              mapping: "$.durationInMs"
  consumes:
    - type: http
      namespace: adf
      baseUri: "https://management.azure.com/subscriptions"
      authentication:
        type: bearer
        token: "$secrets.azure_management_token"
      resources:
        - name: pipeline-runs
          path: "/{{subscription_id}}/resourceGroups/{{resource_group}}/providers/Microsoft.DataFactory/factories/{{factory_name}}/pipelineruns/{{run_id}}"
          inputParameters:
            - name: subscription_id
              in: path
            - name: resource_group
              in: path
            - name: factory_name
              in: path
            - name: run_id
              in: path
          operations:
            - name: get-pipeline-run
              method: GET

Battery Storage System Monitor ▼

renewable battery-storage elasticsearch

Retrieves battery energy storage system (BESS) metrics from the monitoring platform, returning state of charge, discharge rate, temperature, and cycle count.

naftiko: "0.5"
info:
  label: "Battery Storage System Monitor"
  description: "Retrieves battery energy storage system (BESS) metrics from the monitoring platform, returning state of charge, discharge rate, temperature, and cycle count."
  tags:
    - renewable
    - battery-storage
    - elasticsearch
capability:
  exposes:
    - type: mcp
      namespace: battery-storage
      port: 8080
      tools:
        - name: get-bess-metrics
          description: "Look up battery storage system metrics by BESS unit ID."
          inputParameters:
            - name: bess_id
              in: body
              type: string
              description: "The battery energy storage system identifier."
          call: "elasticsearch.get-bess-data"
          with:
            bess_id: "{{bess_id}}"
          outputParameters:
            - name: state_of_charge_pct
              type: string
              mapping: "$.hits.hits[0]._source.soc_pct"
            - name: discharge_rate_mw
              type: string
              mapping: "$.hits.hits[0]._source.discharge_rate_mw"
            - name: temperature_c
              type: string
              mapping: "$.hits.hits[0]._source.temperature_c"
            - name: cycle_count
              type: string
              mapping: "$.hits.hits[0]._source.cycle_count"
  consumes:
    - type: http
      namespace: elasticsearch
      baseUri: "https://nextera-scada.es.amazonaws.com"
      authentication:
        type: bearer
        token: "$secrets.elasticsearch_token"
      resources:
        - name: bess-metrics
          path: "/bess-metrics/_search"
          operations:
            - name: get-bess-data
              method: POST

Billing Dispute Resolution Orchestrator ▼

billing dispute-resolution salesforce teradata sap microsoft-teams

When a customer files a billing dispute, creates a Salesforce case, pulls usage data from Teradata, compares against billed amounts in SAP, and notifies the resolution team via Microsoft Teams.

naftiko: "0.5"
info:
  label: "Billing Dispute Resolution Orchestrator"
  description: "When a customer files a billing dispute, creates a Salesforce case, pulls usage data from Teradata, compares against billed amounts in SAP, and notifies the resolution team via Microsoft Teams."
  tags:
    - billing
    - dispute-resolution
    - salesforce
    - teradata
    - sap
    - microsoft-teams
capability:
  exposes:
    - type: mcp
      namespace: billing-disputes
      port: 8080
      tools:
        - name: process-billing-dispute
          description: "Given an account number, disputed amount, and billing period, create a case, pull usage data, compare, and notify."
          inputParameters:
            - name: account_number
              in: body
              type: string
              description: "The customer account number."
            - name: disputed_amount
              in: body
              type: string
              description: "The disputed billing amount."
            - name: billing_period
              in: body
              type: string
              description: "The billing period in YYYY-MM format."
          steps:
            - name: create-case
              type: call
              call: "salesforce.create-dispute-case"
              with:
                account_number: "{{account_number}}"
                amount: "{{disputed_amount}}"
                period: "{{billing_period}}"
            - name: get-usage
              type: call
              call: "teradata.query-usage"
              with:
                account: "{{account_number}}"
                period: "{{billing_period}}"
            - name: get-billed
              type: call
              call: "sap.get-billing-record"
              with:
                account: "{{account_number}}"
                period: "{{billing_period}}"
            - name: notify-team
              type: call
              call: "msteams.send-message"
              with:
                channel_id: "billing-disputes"
                text: "Billing Dispute: Account {{account_number}}, Period {{billing_period}}. Disputed: ${{disputed_amount}}. Actual usage: {{get-usage.total_kwh}} kWh. Billed: ${{get-billed.billed_amount}}. Case: {{create-case.case_number}}"
  consumes:
    - type: http
      namespace: salesforce
      baseUri: "https://nextera.my.salesforce.com/services/data/v58.0"
      authentication:
        type: bearer
        token: "$secrets.salesforce_token"
      resources:
        - name: cases
          path: "/sobjects/Case"
          operations:
            - name: create-dispute-case
              method: POST
    - type: http
      namespace: teradata
      baseUri: "https://nextera-analytics.teradata.com/api/v1"
      authentication:
        type: bearer
        token: "$secrets.teradata_token"
      resources:
        - name: usage
          path: "/query"
          operations:
            - name: query-usage
              method: POST
    - type: http
      namespace: sap
      baseUri: "https://nextera-s4.sap.com/sap/opu/odata/sap"
      authentication:
        type: basic
        username: "$secrets.sap_user"
        password: "$secrets.sap_password"
      resources:
        - name: billing
          path: "/BILLING_SRV/BillingRecords"
          operations:
            - name: get-billing-record
              method: GET
    - type: http
      namespace: msteams
      baseUri: "https://graph.microsoft.com/v1.0"
      authentication:
        type: bearer
        token: "$secrets.msgraph_token"
      resources:
        - name: channel-messages
          path: "/teams/{{team_id}}/channels/{{channel_id}}/messages"
          inputParameters:
            - name: team_id
              in: path
            - name: channel_id
              in: path
          operations:
            - name: send-message
              method: POST

Boomi Integration Process Status ▼

integration boomi middleware

Checks the status of a Boomi integration process execution, returning process status, start time, and document count.

naftiko: "0.5"
info:
  label: "Boomi Integration Process Status"
  description: "Checks the status of a Boomi integration process execution, returning process status, start time, and document count."
  tags:
    - integration
    - boomi
    - middleware
capability:
  exposes:
    - type: mcp
      namespace: integration
      port: 8080
      tools:
        - name: get-boomi-status
          description: "Check Boomi process execution status."
          inputParameters:
            - name: execution_id
              in: body
              type: string
              description: "The Boomi execution identifier."
          call: "boomi.get-execution"
          with:
            execution_id: "{{execution_id}}"
          outputParameters:
            - name: status
              type: string
              mapping: "$.result[0].status"
            - name: start_time
              type: string
              mapping: "$.result[0].executionTime"
  consumes:
    - type: http
      namespace: boomi
      baseUri: "https://api.boomi.com/api/rest/v1/nextera"
      authentication:
        type: basic
        username: "$secrets.boomi_user"
        password: "$secrets.boomi_password"
      resources:
        - name: executions
          path: "/ExecutionRecord/{{execution_id}}"
          inputParameters:
            - name: execution_id
              in: path
          operations:
            - name: get-execution
              method: GET

Box Document Retrieval ▼

document-management box

Retrieves a document from Box by file ID.

naftiko: "0.5"
info:
  label: "Box Document Retrieval"
  description: "Retrieves a document from Box by file ID."
  tags:
    - document-management
    - box
capability:
  exposes:
    - type: mcp
      namespace: documents
      port: 8080
      tools:
        - name: get-box-document
          description: "Retrieve a Box document by file ID."
          inputParameters:
            - name: file_id
              in: body
              type: string
              description: "The Box file identifier."
          call: "box.get-file"
          with:
            file_id: "{{file_id}}"
          outputParameters:
            - name: file_name
              type: string
              mapping: "$.name"
            - name: size
              type: string
              mapping: "$.size"
  consumes:
    - type: http
      namespace: box
      baseUri: "https://api.box.com/2.0"
      authentication:
        type: bearer
        token: "$secrets.box_token"
      resources:
        - name: files
          path: "/files/{{file_id}}"
          inputParameters:
            - name: file_id
              in: path
          operations:
            - name: get-file
              method: GET

Cisco Webex Meeting Scheduler ▼

collaboration cisco-webex microsoft-teams

Creates a Cisco Webex meeting for cross-team collaboration and sends the join link via Microsoft Teams.

naftiko: "0.5"
info:
  label: "Cisco Webex Meeting Scheduler"
  description: "Creates a Cisco Webex meeting for cross-team collaboration and sends the join link via Microsoft Teams."
  tags:
    - collaboration
    - cisco-webex
    - microsoft-teams
capability:
  exposes:
    - type: mcp
      namespace: collaboration
      port: 8080
      tools:
        - name: schedule-webex-meeting
          description: "Create a Webex meeting and notify via Teams."
          inputParameters:
            - name: title
              in: body
              type: string
              description: "The meeting title."
            - name: start_time
              in: body
              type: string
              description: "Start time in ISO 8601."
            - name: duration
              in: body
              type: string
              description: "Duration in minutes."
          steps:
            - name: create-meeting
              type: call
              call: "webex.create-meeting"
              with:
                title: "{{title}}"
                start: "{{start_time}}"
                duration: "{{duration}}"
            - name: notify-team
              type: call
              call: "msteams.send-message"
              with:
                channel_id: "general"
                text: "Webex meeting: {{title}} at {{start_time}}. Join: {{create-meeting.webLink}}"
  consumes:
    - type: http
      namespace: webex
      baseUri: "https://webexapis.com/v1"
      authentication:
        type: bearer
        token: "$secrets.webex_token"
      resources:
        - name: meetings
          path: "/meetings"
          operations:
            - name: create-meeting
              method: POST
    - type: http
      namespace: msteams
      baseUri: "https://graph.microsoft.com/v1.0"
      authentication:
        type: bearer
        token: "$secrets.msgraph_token"
      resources:
        - name: channel-messages
          path: "/teams/{{team_id}}/channels/{{channel_id}}/messages"
          inputParameters:
            - name: team_id
              in: path
            - name: channel_id
              in: path
          operations:
            - name: send-message
              method: POST

Cloudflare CDN Performance Check ▼

infrastructure cloudflare cdn

Queries Cloudflare analytics for NextEra Energy web properties, returning bandwidth, cache hit ratio, and threat counts.

naftiko: "0.5"
info:
  label: "Cloudflare CDN Performance Check"
  description: "Queries Cloudflare analytics for NextEra Energy web properties, returning bandwidth, cache hit ratio, and threat counts."
  tags:
    - infrastructure
    - cloudflare
    - cdn
capability:
  exposes:
    - type: mcp
      namespace: cdn
      port: 8080
      tools:
        - name: get-cdn-performance
          description: "Retrieve Cloudflare CDN performance metrics for a given zone."
          inputParameters:
            - name: zone_id
              in: body
              type: string
              description: "The Cloudflare zone identifier."
          call: "cloudflare.get-zone-analytics"
          with:
            zone_id: "{{zone_id}}"
          outputParameters:
            - name: bandwidth
              type: string
              mapping: "$.result.totals.bandwidth.all"
            - name: cache_hit_ratio
              type: string
              mapping: "$.result.totals.bandwidth.cached"
            - name: threats
              type: string
              mapping: "$.result.totals.threats.all"
  consumes:
    - type: http
      namespace: cloudflare
      baseUri: "https://api.cloudflare.com/client/v4"
      authentication:
        type: bearer
        token: "$secrets.cloudflare_token"
      resources:
        - name: zone-analytics
          path: "/zones/{{zone_id}}/analytics/dashboard"
          inputParameters:
            - name: zone_id
              in: path
          operations:
            - name: get-zone-analytics
              method: GET

CloudWatch Alarm Status Check ▼

monitoring cloudwatch cloud

Checks the status of AWS CloudWatch alarms for NextEra Energy cloud infrastructure.

naftiko: "0.5"
info:
  label: "CloudWatch Alarm Status Check"
  description: "Checks the status of AWS CloudWatch alarms for NextEra Energy cloud infrastructure."
  tags:
    - monitoring
    - cloudwatch
    - cloud
capability:
  exposes:
    - type: mcp
      namespace: cloud-monitoring
      port: 8080
      tools:
        - name: get-alarm-status
          description: "Check CloudWatch alarm status by alarm name."
          inputParameters:
            - name: alarm_name
              in: body
              type: string
              description: "The CloudWatch alarm name."
          call: "cloudwatch.describe-alarm"
          with:
            alarm_name: "{{alarm_name}}"
          outputParameters:
            - name: state
              type: string
              mapping: "$.MetricAlarms[0].StateValue"
            - name: reason
              type: string
              mapping: "$.MetricAlarms[0].StateReason"
  consumes:
    - type: http
      namespace: cloudwatch
      baseUri: "https://monitoring.us-east-1.amazonaws.com"
      authentication:
        type: aws
        accessKeyId: "$secrets.aws_access_key"
        secretAccessKey: "$secrets.aws_secret_key"
      resources:
        - name: alarms
          path: "/?Action=DescribeAlarms&AlarmNames.member.1={{alarm_name}}"
          inputParameters:
            - name: alarm_name
              in: query
          operations:
            - name: describe-alarm
              method: GET

Confluence Knowledge Base Search ▼

knowledge-management confluence

Searches the NextEra Energy Confluence knowledge base by keyword.

naftiko: "0.5"
info:
  label: "Confluence Knowledge Base Search"
  description: "Searches the NextEra Energy Confluence knowledge base by keyword."
  tags:
    - knowledge-management
    - confluence
capability:
  exposes:
    - type: mcp
      namespace: knowledge
      port: 8080
      tools:
        - name: search-knowledge-base
          description: "Search Confluence knowledge base by keyword."
          inputParameters:
            - name: query
              in: body
              type: string
              description: "The search query."
          call: "confluence.search"
          with:
            query: "{{query}}"
          outputParameters:
            - name: results
              type: array
              mapping: "$.results"
            - name: total_count
              type: string
              mapping: "$.totalSize"
  consumes:
    - type: http
      namespace: confluence
      baseUri: "https://nextera.atlassian.net/wiki/rest/api"
      authentication:
        type: basic
        username: "$secrets.confluence_user"
        password: "$secrets.confluence_api_token"
      resources:
        - name: search
          path: "/search?cql=text~'{{query}}'"
          inputParameters:
            - name: query
              in: query
          operations:
            - name: search
              method: GET

Customer Billing Inquiry Lookup ▼

billing customer-service salesforce-service-cloud

Retrieves a customer billing record from Salesforce Service Cloud by account number, returning current balance, last payment date, and billing cycle.

naftiko: "0.5"
info:
  label: "Customer Billing Inquiry Lookup"
  description: "Retrieves a customer billing record from Salesforce Service Cloud by account number, returning current balance, last payment date, and billing cycle."
  tags:
    - billing
    - customer-service
    - salesforce-service-cloud
capability:
  exposes:
    - type: mcp
      namespace: billing
      port: 8080
      tools:
        - name: get-billing-status
          description: "Look up a customer billing record by account number."
          inputParameters:
            - name: account_number
              in: body
              type: string
              description: "The customer account number."
          call: "salesforce.get-billing"
          with:
            account_number: "{{account_number}}"
          outputParameters:
            - name: current_balance
              type: string
              mapping: "$.Current_Balance__c"
            - name: last_payment_date
              type: string
              mapping: "$.Last_Payment_Date__c"
            - name: billing_cycle
              type: string
              mapping: "$.Billing_Cycle__c"
            - name: account_status
              type: string
              mapping: "$.Account_Status__c"
  consumes:
    - type: http
      namespace: salesforce
      baseUri: "https://nextera.my.salesforce.com/services/data/v58.0"
      authentication:
        type: bearer
        token: "$secrets.salesforce_token"
      resources:
        - name: billing-accounts
          path: "/sobjects/Billing_Account__c/{{account_number}}"
          inputParameters:
            - name: account_number
              in: path
          operations:
            - name: get-billing
              method: GET

Customer Outage Notification Pipeline ▼

grid-ops outage salesforce whatsapp servicenow microsoft-teams

When a grid outage is detected, identifies affected customers in Salesforce, sends SMS notifications via WhatsApp, creates a ServiceNow incident, and posts a status update to Microsoft Teams.

naftiko: "0.5"
info:
  label: "Customer Outage Notification Pipeline"
  description: "When a grid outage is detected, identifies affected customers in Salesforce, sends SMS notifications via WhatsApp, creates a ServiceNow incident, and posts a status update to Microsoft Teams."
  tags:
    - grid-ops
    - outage
    - salesforce
    - whatsapp
    - servicenow
    - microsoft-teams
capability:
  exposes:
    - type: mcp
      namespace: outage-management
      port: 8080
      tools:
        - name: notify-outage
          description: "Given a grid segment ID and estimated restoration time, identify affected customers, send notifications, and create an incident."
          inputParameters:
            - name: segment_id
              in: body
              type: string
              description: "The affected grid segment identifier."
            - name: estimated_restoration
              in: body
              type: string
              description: "Estimated restoration time in ISO 8601 format."
            - name: cause
              in: body
              type: string
              description: "Cause of the outage (weather, equipment, planned)."
          steps:
            - name: get-affected-customers
              type: call
              call: "salesforce.query-segment-customers"
              with:
                segment_id: "{{segment_id}}"
            - name: send-notifications
              type: call
              call: "whatsapp.send-bulk-message"
              with:
                recipients: "{{get-affected-customers.phone_numbers}}"
                message: "NextEra Energy: Power outage in your area. Cause: {{cause}}. Estimated restoration: {{estimated_restoration}}. We apologize for the inconvenience."
            - name: create-incident
              type: call
              call: "servicenow.create-incident"
              with:
                short_description: "Grid Outage: Segment {{segment_id}}"
                category: "outage_management"
                urgency: "1"
                description: "Outage on segment {{segment_id}}. Cause: {{cause}}. Affected customers: {{get-affected-customers.count}}. ERT: {{estimated_restoration}}"
            - name: post-status
              type: call
              call: "msteams.send-message"
              with:
                channel_id: "grid-ops-status"
                text: "OUTAGE ALERT: Segment {{segment_id}}. Cause: {{cause}}. Affected: {{get-affected-customers.count}} customers. ERT: {{estimated_restoration}}. Incident: {{create-incident.number}}"
  consumes:
    - type: http
      namespace: salesforce
      baseUri: "https://nextera.my.salesforce.com/services/data/v58.0"
      authentication:
        type: bearer
        token: "$secrets.salesforce_token"
      resources:
        - name: customers
          path: "/query/?q=SELECT+Id,Phone__c,Name+FROM+Customer_Account__c+WHERE+Grid_Segment__c='{{segment_id}}'"
          inputParameters:
            - name: segment_id
              in: query
          operations:
            - name: query-segment-customers
              method: GET
    - type: http
      namespace: whatsapp
      baseUri: "https://graph.facebook.com/v18.0"
      authentication:
        type: bearer
        token: "$secrets.whatsapp_token"
      resources:
        - name: messages
          path: "/{{phone_number_id}}/messages"
          inputParameters:
            - name: phone_number_id
              in: path
          operations:
            - name: send-bulk-message
              method: POST
    - type: http
      namespace: servicenow
      baseUri: "https://nextera.service-now.com/api/now"
      authentication:
        type: basic
        username: "$secrets.servicenow_user"
        password: "$secrets.servicenow_password"
      resources:
        - name: incidents
          path: "/table/incident"
          operations:
            - name: create-incident
              method: POST
    - type: http
      namespace: msteams
      baseUri: "https://graph.microsoft.com/v1.0"
      authentication:
        type: bearer
        token: "$secrets.msgraph_token"
      resources:
        - name: channel-messages
          path: "/teams/{{team_id}}/channels/{{channel_id}}/messages"
          inputParameters:
            - name: team_id
              in: path
            - name: channel_id
              in: path
          operations:
            - name: send-message
              method: POST

Datadog Infrastructure Health Check ▼

infrastructure monitoring datadog

Queries Datadog for the current health status of NextEra Energy infrastructure, returning host count, alert counts, and critical monitors.

naftiko: "0.5"
info:
  label: "Datadog Infrastructure Health Check"
  description: "Queries Datadog for the current health status of NextEra Energy infrastructure, returning host count, alert counts, and critical monitors."
  tags:
    - infrastructure
    - monitoring
    - datadog
capability:
  exposes:
    - type: mcp
      namespace: infra-monitoring
      port: 8080
      tools:
        - name: get-infra-health
          description: "Retrieve Datadog infrastructure health summary."
          inputParameters:
            - name: environment
              in: body
              type: string
              description: "The environment to check (production, staging)."
          call: "datadog.get-monitors"
          with:
            environment: "{{environment}}"
          outputParameters:
            - name: total_hosts
              type: string
              mapping: "$.total_hosts"
            - name: active_alerts
              type: string
              mapping: "$.alert_count"
            - name: critical_monitors
              type: array
              mapping: "$.critical_monitors"
  consumes:
    - type: http
      namespace: datadog
      baseUri: "https://api.datadoghq.com/api/v1"
      authentication:
        type: apiKey
        key: "$secrets.datadog_api_key"
      resources:
        - name: monitors
          path: "/monitor"
          operations:
            - name: get-monitors
              method: GET

Demand Forecasting Pipeline ▼

grid-ops forecasting teradata azure-machine-learning sharepoint

Generates energy demand forecasts by pulling historical load data from Teradata, weather predictions from the weather API, running the forecast model in Azure Machine Learning, and publishing results to SharePoint for grid planning.

naftiko: "0.5"
info:
  label: "Demand Forecasting Pipeline"
  description: "Generates energy demand forecasts by pulling historical load data from Teradata, weather predictions from the weather API, running the forecast model in Azure Machine Learning, and publishing results to SharePoint for grid planning."
  tags:
    - grid-ops
    - forecasting
    - teradata
    - azure-machine-learning
    - sharepoint
capability:
  exposes:
    - type: mcp
      namespace: demand-forecasting
      port: 8080
      tools:
        - name: generate-demand-forecast
          description: "Given a region and forecast date range, pull load data, weather data, run the model, and publish the forecast."
          inputParameters:
            - name: region
              in: body
              type: string
              description: "The service region (e.g., South Florida, Central Florida)."
            - name: start_date
              in: body
              type: string
              description: "Forecast start date in YYYY-MM-DD."
            - name: end_date
              in: body
              type: string
              description: "Forecast end date in YYYY-MM-DD."
          steps:
            - name: fetch-load-data
              type: call
              call: "teradata.query-historical-load"
              with:
                region: "{{region}}"
                start_date: "{{start_date}}"
                end_date: "{{end_date}}"
            - name: run-forecast
              type: call
              call: "azureml.predict-demand"
              with:
                historical_data: "{{fetch-load-data.results}}"
                region: "{{region}}"
                horizon_start: "{{start_date}}"
                horizon_end: "{{end_date}}"
            - name: publish-forecast
              type: call
              call: "sharepoint.upload-file"
              with:
                site_id: "grid_planning_site"
                folder_path: "DemandForecasts/{{region}}"
                file_name: "forecast_{{start_date}}_{{end_date}}.json"
                content: "{{run-forecast.forecast_data}}"
  consumes:
    - type: http
      namespace: teradata
      baseUri: "https://nextera-analytics.teradata.com/api/v1"
      authentication:
        type: bearer
        token: "$secrets.teradata_token"
      resources:
        - name: queries
          path: "/query"
          operations:
            - name: query-historical-load
              method: POST
    - type: http
      namespace: azureml
      baseUri: "https://nextera-ml.eastus.inference.ml.azure.com"
      authentication:
        type: bearer
        token: "$secrets.azureml_token"
      resources:
        - name: scoring
          path: "/score"
          operations:
            - name: predict-demand
              method: POST
    - type: http
      namespace: sharepoint
      baseUri: "https://graph.microsoft.com/v1.0/sites"
      authentication:
        type: bearer
        token: "$secrets.msgraph_token"
      resources:
        - name: drive-items
          path: "/{{site_id}}/drive/root:/{{folder_path}}/{{file_name}}:/content"
          inputParameters:
            - name: site_id
              in: path
            - name: folder_path
              in: path
            - name: file_name
              in: path
          operations:
            - name: upload-file
              method: PUT

Dynatrace Application Health Check ▼

monitoring dynatrace application-health

Queries Dynatrace for application health metrics for NextEra Energy digital services.

naftiko: "0.5"
info:
  label: "Dynatrace Application Health Check"
  description: "Queries Dynatrace for application health metrics for NextEra Energy digital services."
  tags:
    - monitoring
    - dynatrace
    - application-health
capability:
  exposes:
    - type: mcp
      namespace: app-health
      port: 8080
      tools:
        - name: get-dynatrace-health
          description: "Retrieve Dynatrace application health metrics by entity ID."
          inputParameters:
            - name: entity_id
              in: body
              type: string
              description: "The Dynatrace application entity ID."
          call: "dynatrace.get-app-health"
          with:
            entity_id: "{{entity_id}}"
          outputParameters:
            - name: availability
              type: string
              mapping: "$.result[0].data[0].values[0]"
            - name: response_time
              type: string
              mapping: "$.result[1].data[0].values[0]"
            - name: failure_rate
              type: string
              mapping: "$.result[2].data[0].values[0]"
  consumes:
    - type: http
      namespace: dynatrace
      baseUri: "https://nextera.live.dynatrace.com/api/v2"
      authentication:
        type: bearer
        token: "$secrets.dynatrace_token"
      resources:
        - name: metrics
          path: "/metrics/query"
          operations:
            - name: get-app-health
              method: POST

Employee Onboarding Orchestrator ▼

hr onboarding workday servicenow sharepoint microsoft-teams

On new hire creation in Workday, opens a ServiceNow onboarding ticket, provisions a SharePoint folder, and sends a Microsoft Teams welcome message.

naftiko: "0.5"
info:
  label: "Employee Onboarding Orchestrator"
  description: "On new hire creation in Workday, opens a ServiceNow onboarding ticket, provisions a SharePoint folder, and sends a Microsoft Teams welcome message."
  tags:
    - hr
    - onboarding
    - workday
    - servicenow
    - sharepoint
    - microsoft-teams
capability:
  exposes:
    - type: mcp
      namespace: hr-onboarding
      port: 8080
      tools:
        - name: trigger-onboarding
          description: "Given a Workday employee ID and start date, orchestrate onboarding across ServiceNow, SharePoint, and Microsoft Teams."
          inputParameters:
            - name: workday_employee_id
              in: body
              type: string
              description: "The Workday worker ID."
            - name: start_date
              in: body
              type: string
              description: "Employee start date in YYYY-MM-DD format."
            - name: department
              in: body
              type: string
              description: "The department the new hire is joining."
          steps:
            - name: get-employee
              type: call
              call: "workday.get-worker"
              with:
                worker_id: "{{workday_employee_id}}"
            - name: open-ticket
              type: call
              call: "servicenow.create-incident"
              with:
                short_description: "New hire onboarding: {{get-employee.full_name}}"
                category: "hr_onboarding"
                assigned_group: "IT_Onboarding"
            - name: provision-folder
              type: call
              call: "sharepoint.create-folder"
              with:
                site_id: "hr_onboarding_site"
                folder_path: "OnboardingDocs/{{get-employee.full_name}}_{{start_date}}"
            - name: send-welcome
              type: call
              call: "msteams.send-message"
              with:
                recipient_upn: "{{get-employee.work_email}}"
                text: "Welcome to NextEra Energy, {{get-employee.first_name}}! Your onboarding ticket is {{open-ticket.number}}."
  consumes:
    - type: http
      namespace: workday
      baseUri: "https://wd2-impl-services1.workday.com/ccx/api/v1"
      authentication:
        type: bearer
        token: "$secrets.workday_token"
      resources:
        - name: workers
          path: "/workers/{{worker_id}}"
          inputParameters:
            - name: worker_id
              in: path
          operations:
            - name: get-worker
              method: GET
    - type: http
      namespace: servicenow
      baseUri: "https://nextera.service-now.com/api/now"
      authentication:
        type: basic
        username: "$secrets.servicenow_user"
        password: "$secrets.servicenow_password"
      resources:
        - name: incidents
          path: "/table/incident"
          operations:
            - name: create-incident
              method: POST
    - type: http
      namespace: sharepoint
      baseUri: "https://graph.microsoft.com/v1.0/sites"
      authentication:
        type: bearer
        token: "$secrets.msgraph_token"
      resources:
        - name: drive-items
          path: "/{{site_id}}/drive/root:/{{folder_path}}"
          inputParameters:
            - name: site_id
              in: path
            - name: folder_path
              in: path
          operations:
            - name: create-folder
              method: POST
    - type: http
      namespace: msteams
      baseUri: "https://graph.microsoft.com/v1.0"
      authentication:
        type: bearer
        token: "$secrets.msgraph_token"
      resources:
        - name: messages
          path: "/users/{{recipient_upn}}/sendMail"
          inputParameters:
            - name: recipient_upn
              in: path
          operations:
            - name: send-message
              method: POST

Nextera Energy Workflow 1 ▼

energy operations salesforce