Pfizer Capabilities
Naftiko 0.5 capability definitions for Pfizer - 100 capabilities showing integration workflows and service orchestrations.
Given an adverse event report description, uses Anthropic Claude to assess causality likelihood and severity classification, posting the assessment to the pharmacovigilance Teams channel.
naftiko: "0.5"
info:
label: "AI-Assisted Adverse Event Triage"
description: "Given an adverse event report description, uses Anthropic Claude to assess causality likelihood and severity classification, posting the assessment to the pharmacovigilance Teams channel."
tags:
- ai
- pharmacovigilance
- anthropic
- microsoft-teams
- regulatory
- safety
capability:
exposes:
- type: mcp
namespace: pv-ai
port: 8080
tools:
- name: triage-adverse-event
description: "Given an adverse event narrative and product name, invoke Anthropic Claude to assess causality and severity, then post the AI assessment to the pharmacovigilance Teams channel for human review."
inputParameters:
- name: ae_narrative
in: body
type: string
description: "The full adverse event narrative text to analyze."
- name: product_name
in: body
type: string
description: "The Pfizer product name associated with the adverse event."
- name: teams_channel_id
in: body
type: string
description: "Teams channel ID for the pharmacovigilance team review."
steps:
- name: assess-ae
type: call
call: anthropic.create-message
with:
model: "claude-3-5-sonnet-20241022"
prompt: "You are a pharmacovigilance medical officer. Assess this adverse event for product {{product_name}}. Provide: 1) Causality assessment (Certain/Probable/Possible/Unlikely/Unassessable), 2) Severity (Mild/Moderate/Severe/Life-threatening/Fatal), 3) Seriousness criteria met, 4) Recommended next steps. Narrative: {{ae_narrative}}"
- name: post-assessment
type: call
call: msteams.send-message
with:
channel_id: "{{teams_channel_id}}"
text: "AI Adverse Event Assessment — {{product_name}}:\n{{assess-ae.content}}\n\nIMPORTANT: This is an AI-assisted assessment for triage purposes only. Human review required."
consumes:
- type: http
namespace: anthropic
baseUri: "https://api.anthropic.com/v1"
authentication:
type: apikey
key: "x-api-key"
value: "$secrets.anthropic_api_key"
placement: header
resources:
- name: messages
path: "/messages"
operations:
- name: create-message
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
When Azure Cost Management detects a spend anomaly on a Pfizer subscription, creates a ServiceNow financial incident and posts a FinOps alert to the Microsoft Teams cost management channel.
naftiko: "0.5"
info:
label: "Azure Cloud Cost Anomaly Responder"
description: "When Azure Cost Management detects a spend anomaly on a Pfizer subscription, creates a ServiceNow financial incident and posts a FinOps alert to the Microsoft Teams cost management channel."
tags:
- finops
- cloud
- azure
- servicenow
- microsoft-teams
capability:
exposes:
- type: mcp
namespace: finops
port: 8080
tools:
- name: handle-azure-cost-anomaly
description: "Given an Azure subscription, resource group, and estimated overage in USD, create a ServiceNow financial incident and post an alert to the FinOps Teams channel."
inputParameters:
- name: subscription_id
in: body
type: string
description: "The Azure subscription ID where the cost anomaly was detected."
- name: resource_group
in: body
type: string
description: "The resource group generating the anomalous spend."
- name: estimated_overage_usd
in: body
type: number
description: "Estimated overage in US dollars."
steps:
- name: create-snow-incident
type: call
call: servicenow.create-incident
with:
short_description: "Azure Cost Anomaly — {{resource_group}} — ${{estimated_overage_usd}}"
category: "cloud_cost"
urgency: "2"
- name: post-finops-alert
type: call
call: msteams.send-message
with:
channel_id: "finops-alerts"
text: "Azure Cost Anomaly: {{resource_group}} ({{subscription_id}}) | Overage: ${{estimated_overage_usd}} | SNOW: {{create-snow-incident.number}}"
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Handles Azure Data Factory pipeline failures by creating a ServiceNow incident and notifying the data engineering team for Pfizer.
naftiko: "0.5"
info:
label: "Azure Data Factory Pipeline Failure Handler"
description: "Handles Azure Data Factory pipeline failures by creating a ServiceNow incident and notifying the data engineering team for Pfizer."
tags:
- data-engineering
- azure-data-factory
- servicenow
- monitoring
capability:
exposes:
- type: mcp
namespace: data-engineering
port: 8080
tools:
- name: handle-adf-failure
description: "Given a pipeline run ID and failure details, create a ServiceNow incident and notify the team."
inputParameters:
- name: pipeline_name
in: body
type: string
description: "The ADF pipeline name."
- name: run_id
in: body
type: string
description: "The pipeline run ID."
- name: error_message
in: body
type: string
description: "The error message from the failed run."
steps:
- name: create-incident
type: call
call: servicenow.create-incident
with:
short_description: "ADF Pipeline Failure: {{pipeline_name}}"
description: "Pipeline: {{pipeline_name}} | Run: {{run_id}} | Error: {{error_message}}"
- name: notify-team
type: call
call: msteams.send-message
with:
channel_id: "$secrets.data_eng_channel"
text: "ADF Pipeline FAILURE: {{pipeline_name}} (Run: {{run_id}}). Error: {{error_message}}. SNOW: {{create-incident.number}}."
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves the latest build status from Azure DevOps for a given pipeline in Pfizer CI/CD operations.
naftiko: "0.5"
info:
label: "Azure DevOps Build Status Lookup"
description: "Retrieves the latest build status from Azure DevOps for a given pipeline in Pfizer CI/CD operations."
tags:
- devops
- azure-devops
- ci-cd
- lookup
capability:
exposes:
- type: mcp
namespace: devops-ops
port: 8080
tools:
- name: get-build-status
description: "Given a pipeline ID, return the latest build result, status, and build number."
inputParameters:
- name: pipeline_id
in: body
type: string
description: "The Azure DevOps pipeline definition ID."
call: azdo.get-latest-build
with:
pipeline_id: "{{pipeline_id}}"
outputParameters:
- name: build_number
type: string
mapping: "$.value[0].buildNumber"
- name: result
type: string
mapping: "$.value[0].result"
- name: status
type: string
mapping: "$.value[0].status"
consumes:
- type: http
namespace: azdo
baseUri: "https://dev.azure.com/pfizer"
authentication:
type: bearer
token: "$secrets.azuredevops_token"
resources:
- name: builds
path: "/_apis/build/builds?definitions={{pipeline_id}}&$top=1&api-version=7.0"
inputParameters:
- name: pipeline_id
in: query
operations:
- name: get-latest-build
method: GET
Orchestrates the clinical database lock process by verifying data completeness in Snowflake, updating status in Veeva Vault, and notifying stakeholders for Pfizer.
naftiko: "0.5"
info:
label: "Clinical Data Lock Orchestrator"
description: "Orchestrates the clinical database lock process by verifying data completeness in Snowflake, updating status in Veeva Vault, and notifying stakeholders for Pfizer."
tags:
- clinical-trials
- data-management
- snowflake
- veeva-vault
capability:
exposes:
- type: mcp
namespace: clinical-data-mgmt
port: 8080
tools:
- name: execute-data-lock
description: "Given a study ID and database identifier, verify completeness, update lock status, and notify the team."
inputParameters:
- name: study_id
in: body
type: string
description: "The clinical study protocol number."
- name: database_id
in: body
type: string
description: "The clinical database identifier."
- name: lock_type
in: body
type: string
description: "Lock type (soft-lock, hard-lock)."
steps:
- name: verify-completeness
type: call
call: snowflake.execute-query
with:
statement: "SELECT COUNT(*) as open_queries FROM data_queries WHERE study_id = '{{study_id}}' AND status = 'Open'"
warehouse: "CLINICAL_WH"
- name: update-vault-status
type: call
call: veeva.update-object-record
with:
object_type: "study_database__c"
id: "{{database_id}}"
lock_status__c: "{{lock_type}}"
- name: notify-team
type: call
call: msteams.send-message
with:
channel_id: "$secrets.cdm_channel"
text: "Database Lock: Study {{study_id}} — {{lock_type}} initiated. Open queries: {{verify-completeness.data}}. Vault updated."
consumes:
- type: http
namespace: snowflake
baseUri: "https://pfizer.snowflakecomputing.com/api/v2"
authentication:
type: bearer
token: "$secrets.snowflake_token"
resources:
- name: statements
path: "/statements"
operations:
- name: execute-query
method: POST
- type: http
namespace: veeva
baseUri: "https://pfizer.veevavault.com/api/v24.1"
authentication:
type: bearer
token: "$secrets.veeva_token"
resources:
- name: object-records
path: "/vobjects/{{object_type}}"
inputParameters:
- name: object_type
in: path
operations:
- name: create-object-record
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Reconciles clinical data between Veeva Vault and Snowflake, logs discrepancies in Jira, and alerts the data management team for Pfizer.
naftiko: "0.5"
info:
label: "Clinical Data Reconciliation Checker"
description: "Reconciles clinical data between Veeva Vault and Snowflake, logs discrepancies in Jira, and alerts the data management team for Pfizer."
tags:
- clinical-trials
- data-management
- veeva-vault
- snowflake
capability:
exposes:
- type: mcp
namespace: clinical-data-quality
port: 8080
tools:
- name: reconcile-clinical-data
description: "Given a study ID, compare record counts between Veeva Vault and Snowflake and report discrepancies."
inputParameters:
- name: study_id
in: body
type: string
description: "The clinical study protocol number."
- name: data_domain
in: body
type: string
description: "Data domain to reconcile (demographics, adverse-events, labs)."
steps:
- name: query-vault
type: call
call: veeva.query-submissions
with:
query: "SELECT COUNT(*) FROM {{data_domain}}__c WHERE study_id__c = '{{study_id}}'"
- name: query-snowflake
type: call
call: snowflake.execute-query
with:
statement: "SELECT COUNT(*) as cnt FROM {{data_domain}} WHERE study_id = '{{study_id}}'"
warehouse: "CLINICAL_WH"
- name: log-discrepancy
type: call
call: jira.create-issue
with:
project: "CDM"
summary: "Data Reconciliation: {{study_id}} — {{data_domain}}"
issuetype: "Bug"
- name: alert-team
type: call
call: msteams.send-message
with:
channel_id: "$secrets.cdm_channel"
text: "Data Reconciliation for Study {{study_id}} ({{data_domain}}): Vault={{query-vault.totalCount}}, Snowflake={{query-snowflake.data}}. Jira: {{log-discrepancy.key}}."
consumes:
- type: http
namespace: veeva
baseUri: "https://pfizer.veevavault.com/api/v24.1"
authentication:
type: bearer
token: "$secrets.veeva_token"
resources:
- name: object-records
path: "/vobjects/{{object_type}}"
inputParameters:
- name: object_type
in: path
operations:
- name: create-object-record
method: POST
- type: http
namespace: snowflake
baseUri: "https://pfizer.snowflakecomputing.com/api/v2"
authentication:
type: bearer
token: "$secrets.snowflake_token"
resources:
- name: statements
path: "/statements"
operations:
- name: execute-query
method: POST
- type: http
namespace: jira
baseUri: "https://pfizer.atlassian.net/rest/api/3"
authentication:
type: bearer
token: "$secrets.jira_token"
resources:
- name: issues
path: "/issue"
operations:
- name: create-issue
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Tracks IRB approval status for clinical sites by querying Veeva Vault, updating Jira, and notifying the regulatory team for Pfizer.
naftiko: "0.5"
info:
label: "Clinical IRB Approval Tracking Orchestrator"
description: "Tracks IRB approval status for clinical sites by querying Veeva Vault, updating Jira, and notifying the regulatory team for Pfizer."
tags:
- clinical-trials
- regulatory
- veeva-vault
- jira
capability:
exposes:
- type: mcp
namespace: clinical-regulatory
port: 8080
tools:
- name: track-irb-approvals
description: "Given a study ID, check IRB approval status across sites, update tracking, and notify the team."
inputParameters:
- name: study_id
in: body
type: string
description: "The clinical study protocol number."
- name: region
in: body
type: string
description: "The geographic region to check."
steps:
- name: query-irb-status
type: call
call: veeva.query-submissions
with:
query: "SELECT site_id__c, irb_status__c FROM irb_submission__c WHERE study_id__c = '{{study_id}}' AND region__c = '{{region}}'"
- name: update-tracker
type: call
call: jira.create-issue
with:
project: "REG"
summary: "IRB Status Update: Study {{study_id}} — {{region}}"
issuetype: "Task"
- name: notify-team
type: call
call: msteams.send-message
with:
channel_id: "$secrets.regulatory_channel"
text: "IRB Approval Status for Study {{study_id}} ({{region}}): {{query-irb-status.totalCount}} sites tracked. Jira: {{update-tracker.key}}."
consumes:
- type: http
namespace: veeva
baseUri: "https://pfizer.veevavault.com/api/v24.1"
authentication:
type: bearer
token: "$secrets.veeva_token"
resources:
- name: query
path: "/query"
operations:
- name: query-submissions
method: POST
- type: http
namespace: jira
baseUri: "https://pfizer.atlassian.net/rest/api/3"
authentication:
type: bearer
token: "$secrets.jira_token"
resources:
- name: issues
path: "/issue"
operations:
- name: create-issue
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Processes clinical protocol amendments by updating Veeva Vault, creating Jira tracking tasks, and notifying the clinical team for Pfizer.
naftiko: "0.5"
info:
label: "Clinical Protocol Amendment Processor"
description: "Processes clinical protocol amendments by updating Veeva Vault, creating Jira tracking tasks, and notifying the clinical team for Pfizer."
tags:
- clinical-trials
- veeva-vault
- jira
- regulatory
capability:
exposes:
- type: mcp
namespace: clinical-regulatory
port: 8080
tools:
- name: process-protocol-amendment
description: "Given protocol amendment details, update the document in Veeva Vault, create a Jira task, and notify affected teams."
inputParameters:
- name: study_id
in: body
type: string
description: "The clinical study protocol number."
- name: amendment_number
in: body
type: string
description: "The amendment version number."
- name: amendment_summary
in: body
type: string
description: "Summary of protocol changes."
- name: impacted_sites
in: body
type: string
description: "Comma-separated list of impacted site IDs."
steps:
- name: update-vault
type: call
call: veeva.create-object-record
with:
object_type: "protocol_amendment__c"
study_id__c: "{{study_id}}"
amendment_number__c: "{{amendment_number}}"
- name: create-jira-task
type: call
call: jira.create-issue
with:
project: "CLIN"
summary: "Protocol Amendment {{amendment_number}} for Study {{study_id}}"
issuetype: "Task"
- name: notify-team
type: call
call: msteams.send-message
with:
channel_id: "$secrets.clinical_ops_channel"
text: "Protocol Amendment {{amendment_number}} for Study {{study_id}} processed. Impacted sites: {{impacted_sites}}. Jira: {{create-jira-task.key}}."
consumes:
- type: http
namespace: veeva
baseUri: "https://pfizer.veevavault.com/api/v24.1"
authentication:
type: bearer
token: "$secrets.veeva_token"
resources:
- name: object-records
path: "/vobjects/{{object_type}}"
inputParameters:
- name: object_type
in: path
operations:
- name: create-object-record
method: POST
- type: http
namespace: jira
baseUri: "https://pfizer.atlassian.net/rest/api/3"
authentication:
type: bearer
token: "$secrets.jira_token"
resources:
- name: issues
path: "/issue"
operations:
- name: create-issue
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Monitors the clinical trial randomization system by checking Snowflake data integrity and alerting the biostatistics team for Pfizer.
naftiko: "0.5"
info:
label: "Clinical Randomization System Monitor"
description: "Monitors the clinical trial randomization system by checking Snowflake data integrity and alerting the biostatistics team for Pfizer."
tags:
- clinical-trials
- snowflake
- biostatistics
- monitoring
capability:
exposes:
- type: mcp
namespace: clinical-biostats
port: 8080
tools:
- name: monitor-randomization
description: "Given a study ID, verify randomization data integrity in Snowflake and alert if anomalies are detected."
inputParameters:
- name: study_id
in: body
type: string
description: "The clinical study protocol number."
- name: randomization_scheme
in: body
type: string
description: "The randomization scheme identifier."
steps:
- name: check-integrity
type: call
call: snowflake.execute-query
with:
statement: "CALL check_randomization_integrity('{{study_id}}', '{{randomization_scheme}}')"
warehouse: "CLINICAL_WH"
- name: create-alert
type: call
call: servicenow.create-incident
with:
short_description: "Randomization Monitor: Study {{study_id}}"
category: "clinical_biostats"
description: "Study: {{study_id}} | Scheme: {{randomization_scheme}} | Status: {{check-integrity.data}}"
- name: notify-biostats
type: call
call: msteams.send-message
with:
channel_id: "$secrets.biostats_channel"
text: "Randomization Monitor: Study {{study_id}} ({{randomization_scheme}}). Integrity check: {{check-integrity.data}}. SNOW: {{create-alert.number}}."
consumes:
- type: http
namespace: snowflake
baseUri: "https://pfizer.snowflakecomputing.com/api/v2"
authentication:
type: bearer
token: "$secrets.snowflake_token"
resources:
- name: statements
path: "/statements"
operations:
- name: execute-query
method: POST
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Processes Suspected Unexpected Serious Adverse Reactions by logging in Veeva Vault, creating urgent ServiceNow cases, and alerting the DSMB for Pfizer.
naftiko: "0.5"
info:
label: "Clinical Safety Reporting SUSAR Handler"
description: "Processes Suspected Unexpected Serious Adverse Reactions by logging in Veeva Vault, creating urgent ServiceNow cases, and alerting the DSMB for Pfizer."
tags:
- drug-safety
- clinical-trials
- veeva-vault
- regulatory
capability:
exposes:
- type: mcp
namespace: clinical-safety
port: 8080
tools:
- name: process-susar
description: "Given SUSAR details, log in Veeva Vault, create an urgent ServiceNow case, and alert the DSMB."
inputParameters:
- name: study_id
in: body
type: string
description: "The clinical study protocol number."
- name: patient_id
in: body
type: string
description: "Anonymized patient identifier."
- name: event_term
in: body
type: string
description: "The adverse event MedDRA preferred term."
- name: seriousness_criteria
in: body
type: string
description: "Seriousness criteria met."
steps:
- name: log-in-vault
type: call
call: veeva.create-object-record
with:
object_type: "safety_case__c"
study_id__c: "{{study_id}}"
patient_id__c: "{{patient_id}}"
event_term__c: "{{event_term}}"
- name: create-urgent-case
type: call
call: servicenow.create-incident
with:
short_description: "SUSAR: {{event_term}} — Study {{study_id}}"
priority: "1"
- name: alert-dsmb
type: call
call: msteams.send-message
with:
channel_id: "$secrets.dsmb_channel"
text: "URGENT SUSAR: {{event_term}} in Study {{study_id}} (Patient {{patient_id}}). Seriousness: {{seriousness_criteria}}. Vault: {{log-in-vault.id}}. SNOW: {{create-urgent-case.number}}."
consumes:
- type: http
namespace: veeva
baseUri: "https://pfizer.veevavault.com/api/v24.1"
authentication:
type: bearer
token: "$secrets.veeva_token"
resources:
- name: object-records
path: "/vobjects/{{object_type}}"
inputParameters:
- name: object_type
in: path
operations:
- name: create-object-record
method: POST
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Creates monitoring visit schedules in Veeva Vault, assigns tasks in Jira, and notifies the CRA team for Pfizer.
naftiko: "0.5"
info:
label: "Clinical Site Monitoring Visit Scheduler"
description: "Creates monitoring visit schedules in Veeva Vault, assigns tasks in Jira, and notifies the CRA team for Pfizer."
tags:
- clinical-trials
- veeva-vault
- jira
- scheduling
capability:
exposes:
- type: mcp
namespace: clinical-monitoring
port: 8080
tools:
- name: schedule-monitoring-visit
description: "Given site and visit details, create a Veeva Vault record, a Jira task, and a Teams notification."
inputParameters:
- name: site_id
in: body
type: string
description: "The clinical site identifier."
- name: visit_type
in: body
type: string
description: "Type of monitoring visit (routine, for-cause, closeout)."
- name: visit_date
in: body
type: string
description: "Scheduled date for the visit."
- name: cra_name
in: body
type: string
description: "Name of the assigned CRA."
steps:
- name: create-vault-record
type: call
call: veeva.create-object-record
with:
object_type: "monitoring_visit__c"
site_id__c: "{{site_id}}"
visit_type__c: "{{visit_type}}"
visit_date__c: "{{visit_date}}"
- name: create-jira-task
type: call
call: jira.create-issue
with:
project: "CLIN"
summary: "Monitoring Visit: {{visit_type}} at Site {{site_id}} on {{visit_date}}"
issuetype: "Task"
- name: notify-cra-team
type: call
call: msteams.send-message
with:
channel_id: "$secrets.cra_channel"
text: "New {{visit_type}} monitoring visit at Site {{site_id}} on {{visit_date}}. CRA: {{cra_name}}. Jira: {{create-jira-task.key}}."
consumes:
- type: http
namespace: veeva
baseUri: "https://pfizer.veevavault.com/api/v24.1"
authentication:
type: bearer
token: "$secrets.veeva_token"
resources:
- name: object-records
path: "/vobjects/{{object_type}}"
inputParameters:
- name: object_type
in: path
operations:
- name: create-object-record
method: POST
- type: http
namespace: jira
baseUri: "https://pfizer.atlassian.net/rest/api/3"
authentication:
type: bearer
token: "$secrets.jira_token"
resources:
- name: issues
path: "/issue"
operations:
- name: create-issue
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Tracks clinical study budgets by pulling actuals from SAP, comparing to plan in Snowflake, and notifying finance for Pfizer.
naftiko: "0.5"
info:
label: "Clinical Study Budget Tracker"
description: "Tracks clinical study budgets by pulling actuals from SAP, comparing to plan in Snowflake, and notifying finance for Pfizer."
tags:
- clinical-trials
- finance
- sap
- snowflake
capability:
exposes:
- type: mcp
namespace: clinical-finance
port: 8080
tools:
- name: track-study-budget
description: "Given a study ID and fiscal period, pull actuals from SAP, compare to budget, and alert on variances."
inputParameters:
- name: study_id
in: body
type: string
description: "The clinical study protocol number."
- name: fiscal_period
in: body
type: string
description: "The fiscal period to analyze."
steps:
- name: get-actuals
type: call
call: sap.get-cost-report
with:
study_id: "{{study_id}}"
period: "{{fiscal_period}}"
- name: get-budget
type: call
call: snowflake.execute-query
with:
statement: "SELECT budget_amount, study_id FROM clinical_budgets WHERE study_id = '{{study_id}}' AND period = '{{fiscal_period}}'"
warehouse: "FINANCE_WH"
- name: notify-finance
type: call
call: msteams.send-message
with:
channel_id: "$secrets.clinical_finance_channel"
text: "Study Budget Alert: {{study_id}} for {{fiscal_period}}. Actuals: {{get-actuals.total}}. Budget: {{get-budget.data}}."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_COSTCENTER_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: get-record
method: GET
- type: http
namespace: snowflake
baseUri: "https://pfizer.snowflakecomputing.com/api/v2"
authentication:
type: bearer
token: "$secrets.snowflake_token"
resources:
- name: statements
path: "/statements"
operations:
- name: execute-query
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Monitors Veeva Vault clinical data submissions for quality exceptions and creates a ServiceNow task for the data management team when exceptions are detected.
naftiko: "0.5"
info:
label: "Clinical Trial Data Quality Alert"
description: "Monitors Veeva Vault clinical data submissions for quality exceptions and creates a ServiceNow task for the data management team when exceptions are detected."
tags:
- clinical-trials
- data-quality
- servicenow
- microsoft-teams
- compliance
capability:
exposes:
- type: mcp
namespace: clinical-ops
port: 8080
tools:
- name: handle-data-quality-exception
description: "Given a clinical study ID and data exception type, create a ServiceNow data management task and notify the clinical data team via Teams."
inputParameters:
- name: study_id
in: body
type: string
description: "The clinical study identifier (protocol number)."
- name: exception_type
in: body
type: string
description: "The type of data quality exception (e.g., 'Missing Query', 'Protocol Deviation', 'Data Lock Failure')."
- name: site_id
in: body
type: string
description: "The clinical site identifier where the exception occurred."
- name: teams_channel_id
in: body
type: string
description: "Teams channel ID for the clinical data management team."
steps:
- name: create-dm-task
type: call
call: servicenow.create-incident
with:
short_description: "Clinical Data Exception: {{exception_type}} — Study {{study_id}}"
category: "clinical_data_management"
description: "Study: {{study_id}} | Site: {{site_id}} | Exception: {{exception_type}}"
- name: notify-cdm-team
type: call
call: msteams.send-message
with:
channel_id: "{{teams_channel_id}}"
text: "Clinical Data Alert: {{exception_type}} in Study {{study_id}} at Site {{site_id}}. SNOW task: {{create-dm-task.number}}. Please review and resolve."
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Queries Snowflake for current enrollment figures by study, generates a summary, and posts to the clinical operations Teams channel for Pfizer.
naftiko: "0.5"
info:
label: "Clinical Trial Enrollment Status Reporter"
description: "Queries Snowflake for current enrollment figures by study, generates a summary, and posts to the clinical operations Teams channel for Pfizer."
tags:
- clinical-trials
- snowflake
- microsoft-teams
- reporting
capability:
exposes:
- type: mcp
namespace: clinical-ops
port: 8080
tools:
- name: report-enrollment-status
description: "Given a study ID, query enrollment data, format a summary, and post to the designated Teams channel."
inputParameters:
- name: study_id
in: body
type: string
description: "The clinical study protocol number."
- name: teams_channel_id
in: body
type: string
description: "Teams channel ID for clinical operations."
steps:
- name: query-enrollment
type: call
call: snowflake.execute-query
with:
statement: "SELECT site_id, enrolled_count, target FROM enrollment_tracker WHERE study_id = '{{study_id}}'"
warehouse: "CLINICAL_WH"
- name: post-summary
type: call
call: msteams.send-message
with:
channel_id: "{{teams_channel_id}}"
text: "Enrollment Status for Study {{study_id}}: {{query-enrollment.data}}"
consumes:
- type: http
namespace: snowflake
baseUri: "https://pfizer.snowflakecomputing.com/api/v2"
authentication:
type: bearer
token: "$secrets.snowflake_token"
resources:
- name: statements
path: "/statements"
operations:
- name: execute-query
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Handles cold chain temperature excursions by logging in SAP, creating a quality incident, and alerting logistics and quality teams for Pfizer.
naftiko: "0.5"
info:
label: "Cold Chain Temperature Excursion Handler"
description: "Handles cold chain temperature excursions by logging in SAP, creating a quality incident, and alerting logistics and quality teams for Pfizer."
tags:
- supply-chain
- cold-chain
- quality
- sap
capability:
exposes:
- type: mcp
namespace: cold-chain-ops
port: 8080
tools:
- name: handle-temp-excursion
description: "Given temperature excursion details, log in SAP, create a ServiceNow quality incident, and alert teams."
inputParameters:
- name: shipment_id
in: body
type: string
description: "The shipment identifier."
- name: product_name
in: body
type: string
description: "The product being shipped."
- name: temperature_reading
in: body
type: string
description: "The temperature reading."
- name: acceptable_range
in: body
type: string
description: "The acceptable temperature range."
- name: duration_minutes
in: body
type: integer
description: "Duration of excursion in minutes."
steps:
- name: log-sap-excursion
type: call
call: sap.create-quality-notification
with:
notification_type: "Q2"
description: "Cold Chain Excursion: Shipment {{shipment_id}}, Product {{product_name}}, Temp {{temperature_reading}}"
- name: create-quality-incident
type: call
call: servicenow.create-incident
with:
short_description: "Cold Chain Excursion: {{product_name}} — Shipment {{shipment_id}}"
priority: "2"
- name: alert-teams
type: call
call: msteams.send-message
with:
channel_id: "$secrets.cold_chain_channel"
text: "COLD CHAIN ALERT: Temp excursion for {{product_name}} (Shipment {{shipment_id}}). Reading: {{temperature_reading}} (range: {{acceptable_range}}). SAP: {{log-sap-excursion.notification_number}}. SNOW: {{create-quality-incident.number}}."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_QUALITYNOTIFICATION_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: create-record
method: POST
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Tracks compliance audit findings by creating Jira issues from ServiceNow audit records and notifying the compliance team for Pfizer.
naftiko: "0.5"
info:
label: "Compliance Audit Finding Tracker"
description: "Tracks compliance audit findings by creating Jira issues from ServiceNow audit records and notifying the compliance team for Pfizer."
tags:
- compliance
- servicenow
- jira
- audit
capability:
exposes:
- type: mcp
namespace: compliance-audit
port: 8080
tools:
- name: track-audit-findings
description: "Given an audit ID, pull findings from ServiceNow, create Jira tracking issues, and notify the compliance team."
inputParameters:
- name: audit_id
in: body
type: string
description: "The ServiceNow audit ID."
- name: audit_type
in: body
type: string
description: "Type of audit (internal, external, regulatory)."
steps:
- name: get-findings
type: call
call: servicenow.get-audit-findings
with:
audit_id: "{{audit_id}}"
- name: create-jira-epic
type: call
call: jira.create-issue
with:
project: "COMP"
summary: "Audit Findings: {{audit_type}} Audit {{audit_id}} — {{get-findings.count}} findings"
issuetype: "Epic"
- name: notify-compliance
type: call
call: msteams.send-message
with:
channel_id: "$secrets.compliance_audit_channel"
text: "Audit Findings: {{audit_type}} Audit {{audit_id}} has {{get-findings.count}} findings. Jira Epic: {{create-jira-epic.key}}."
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.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: jira
baseUri: "https://pfizer.atlassian.net/rest/api/3"
authentication:
type: bearer
token: "$secrets.jira_token"
resources:
- name: issues
path: "/issue"
operations:
- name: create-issue
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Searches Pfizer Confluence knowledge base for regulatory guidance documents by keyword.
naftiko: "0.5"
info:
label: "Confluence Regulatory Knowledge Search"
description: "Searches Pfizer Confluence knowledge base for regulatory guidance documents by keyword."
tags:
- regulatory
- confluence
- knowledge-management
- search
capability:
exposes:
- type: mcp
namespace: regulatory-kb
port: 8080
tools:
- name: search-regulatory-docs
description: "Given a search query, return matching Confluence pages with titles, space keys, and URLs."
inputParameters:
- name: search_query
in: body
type: string
description: "The search query for regulatory guidance documents."
call: confluence.search-content
with:
search_query: "{{search_query}}"
outputParameters:
- name: results
type: array
mapping: "$.results"
- name: total_size
type: integer
mapping: "$.totalSize"
consumes:
- type: http
namespace: confluence
baseUri: "https://pfizer.atlassian.net/wiki/rest/api"
authentication:
type: bearer
token: "$secrets.confluence_token"
resources:
- name: search
path: "/content/search?cql=text~'{{search_query}}'"
inputParameters:
- name: search_query
in: query
operations:
- name: search-content
method: GET
Orchestrates ML model deployment by promoting a model in Databricks, updating the model registry, and notifying the data science team for Pfizer.
naftiko: "0.5"
info:
label: "Databricks ML Model Deployment Pipeline"
description: "Orchestrates ML model deployment by promoting a model in Databricks, updating the model registry, and notifying the data science team for Pfizer."
tags:
- r-and-d
- databricks
- machine-learning
- deployment
capability:
exposes:
- type: mcp
namespace: rd-ml-ops
port: 8080
tools:
- name: deploy-ml-model
description: "Given a model name and version, promote in Databricks MLflow, register in the model registry, and notify the team."
inputParameters:
- name: model_name
in: body
type: string
description: "The MLflow model name."
- name: model_version
in: body
type: string
description: "The model version to promote."
- name: target_stage
in: body
type: string
description: "Target stage (Staging, Production)."
steps:
- name: promote-model
type: call
call: databricks.transition-model-stage
with:
name: "{{model_name}}"
version: "{{model_version}}"
stage: "{{target_stage}}"
- name: log-deployment
type: call
call: servicenow.create-incident
with:
short_description: "ML Model Deployment: {{model_name}} v{{model_version}} to {{target_stage}}"
category: "ml_ops"
- name: notify-ds-team
type: call
call: msteams.send-message
with:
channel_id: "$secrets.data_science_channel"
text: "ML Model Deployed: {{model_name}} v{{model_version}} promoted to {{target_stage}}. SNOW: {{log-deployment.number}}."
consumes:
- type: http
namespace: databricks
baseUri: "https://pfizer.cloud.databricks.com/api/2.0"
authentication:
type: bearer
token: "$secrets.databricks_token"
resources:
- name: model-versions
path: "/mlflow/model-versions/transition-stage"
operations:
- name: transition-model-stage
method: POST
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Fetches current Datadog monitor status for a given application service and returns the count of critical, warning, and OK monitors.
naftiko: "0.5"
info:
label: "Datadog Application Performance Monitor"
description: "Fetches current Datadog monitor status for a given application service and returns the count of critical, warning, and OK monitors."
tags:
- observability
- datadog
- monitoring
- lookup
capability:
exposes:
- type: mcp
namespace: apm-lookup
port: 8080
tools:
- name: get-app-monitor-status
description: "Given a Datadog service tag, list all monitors scoped to that service and return counts by status (OK, Warning, Critical, No Data)."
inputParameters:
- name: service_tag
in: body
type: string
description: "The Datadog service tag to filter monitors (e.g., 'service:pfizer-ecommerce')."
call: datadog.get-monitors
with:
tags: "{{service_tag}}"
outputParameters:
- name: critical_count
type: integer
mapping: "$.critical_count"
- name: warning_count
type: integer
mapping: "$.warning_count"
- name: ok_count
type: integer
mapping: "$.ok_count"
consumes:
- type: http
namespace: datadog
baseUri: "https://api.datadoghq.com/api/v1"
authentication:
type: apikey
key: "DD-API-KEY"
value: "$secrets.datadog_api_key"
placement: header
resources:
- name: monitors
path: "/monitor"
inputParameters:
- name: tags
in: query
operations:
- name: get-monitors
method: GET
Retrieves the current health status of a monitored service from Datadog for Pfizer SRE operations.
naftiko: "0.5"
info:
label: "Datadog Service Health Check"
description: "Retrieves the current health status of a monitored service from Datadog for Pfizer SRE operations."
tags:
- monitoring
- datadog
- sre
- health-check
capability:
exposes:
- type: mcp
namespace: sre-ops
port: 8080
tools:
- name: get-service-health
description: "Given a service name, return the overall status, number of active monitors, and last check time."
inputParameters:
- name: service_name
in: body
type: string
description: "The Datadog service name."
call: datadog.get-service-status
with:
service_name: "{{service_name}}"
outputParameters:
- name: overall_status
type: string
mapping: "$.overall_status"
- name: active_monitors
type: integer
mapping: "$.counts.total"
- name: last_triggered
type: string
mapping: "$.last_triggered_ts"
consumes:
- type: http
namespace: datadog
baseUri: "https://api.datadoghq.com/api/v1"
authentication:
type: bearer
token: "$secrets.datadog_api_key"
resources:
- name: monitors
path: "/monitor/search?query=service:{{service_name}}"
inputParameters:
- name: service_name
in: query
operations:
- name: get-service-status
method: GET
When a Datadog SLO drops below its error budget threshold, creates a ServiceNow incident and alerts the platform reliability team in Microsoft Teams.
naftiko: "0.5"
info:
label: "Datadog SLO Breach Alert"
description: "When a Datadog SLO drops below its error budget threshold, creates a ServiceNow incident and alerts the platform reliability team in Microsoft Teams."
tags:
- observability
- datadog
- slo
- servicenow
- incident-response
- microsoft-teams
capability:
exposes:
- type: mcp
namespace: slo-ops
port: 8080
tools:
- name: handle-slo-breach
description: "Given a Datadog SLO ID, SLO name, and current compliance percentage, create a ServiceNow incident and alert the platform team in Teams that the SLO error budget is breached."
inputParameters:
- name: slo_id
in: body
type: string
description: "The Datadog SLO ID that has breached its error budget."
- name: slo_name
in: body
type: string
description: "The human-readable SLO name."
- name: current_compliance
in: body
type: number
description: "The current SLO compliance percentage (e.g., 98.7)."
- name: teams_channel_id
in: body
type: string
description: "Teams channel ID for the platform reliability alert."
steps:
- name: create-incident
type: call
call: servicenow.create-incident
with:
short_description: "SLO Breach: {{slo_name}} at {{current_compliance}}%"
category: "slo_breach"
urgency: "2"
- name: alert-platform-team
type: call
call: msteams.send-message
with:
channel_id: "{{teams_channel_id}}"
text: "SLO ERROR BUDGET BREACH: {{slo_name}} | Current compliance: {{current_compliance}}% | SNOW: {{create-incident.number}} | SLO ID: {{slo_id}}"
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Initiates periodic SOP review cycles by identifying documents due for review in Veeva Vault, creating Jira tasks, and notifying owners for Pfizer.
naftiko: "0.5"
info:
label: "Document Control SOP Review Cycle Initiator"
description: "Initiates periodic SOP review cycles by identifying documents due for review in Veeva Vault, creating Jira tasks, and notifying owners for Pfizer."
tags:
- quality
- document-control
- veeva-vault
- jira
capability:
exposes:
- type: mcp
namespace: doc-control
port: 8080
tools:
- name: initiate-sop-review-cycle
description: "Given a document category and review period, find SOPs due for review, create tracking tasks, and notify owners."
inputParameters:
- name: document_category
in: body
type: string
description: "The SOP document category (manufacturing, QC, clinical)."
- name: review_due_days
in: body
type: integer
description: "Days until review due date to include."
steps:
- name: find-docs-due
type: call
call: veeva.query-submissions
with:
query: "SELECT id, name__v FROM documents WHERE category__c = '{{document_category}}'"
- name: create-jira-tasks
type: call
call: jira.create-issue
with:
project: "QMS"
summary: "SOP Review Cycle: {{document_category}} — {{find-docs-due.totalCount}} documents"
issuetype: "Task"
- name: notify-owners
type: call
call: msteams.send-message
with:
channel_id: "$secrets.doc_control_channel"
text: "SOP Review Cycle: {{find-docs-due.totalCount}} {{document_category}} documents due within {{review_due_days}} days. Jira: {{create-jira-tasks.key}}."
consumes:
- type: http
namespace: veeva
baseUri: "https://pfizer.veevavault.com/api/v24.1"
authentication:
type: bearer
token: "$secrets.veeva_token"
resources:
- name: object-records
path: "/vobjects/{{object_type}}"
inputParameters:
- name: object_type
in: path
operations:
- name: create-object-record
method: POST
- type: http
namespace: jira
baseUri: "https://pfizer.atlassian.net/rest/api/3"
authentication:
type: bearer
token: "$secrets.jira_token"
resources:
- name: issues
path: "/issue"
operations:
- name: create-issue
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Receives an adverse event report, creates a pharmacovigilance case in ServiceNow, and notifies the drug safety team via Teams for Pfizer.
naftiko: "0.5"
info:
label: "Drug Safety Adverse Event Report Processor"
description: "Receives an adverse event report, creates a pharmacovigilance case in ServiceNow, and notifies the drug safety team via Teams for Pfizer."
tags:
- drug-safety
- pharmacovigilance
- servicenow
- compliance
capability:
exposes:
- type: mcp
namespace: drug-safety
port: 8080
tools:
- name: process-adverse-event
description: "Given adverse event details, create a PV case in ServiceNow and send an urgent notification to the drug safety officer."
inputParameters:
- name: patient_id
in: body
type: string
description: "Anonymized patient identifier."
- name: product_name
in: body
type: string
description: "The drug product name."
- name: event_description
in: body
type: string
description: "Description of the adverse event."
- name: severity
in: body
type: string
description: "Severity classification (mild, moderate, severe, life-threatening)."
steps:
- name: create-pv-case
type: call
call: servicenow.create-incident
with:
short_description: "AE Report: {{product_name}} — {{severity}}"
category: "pharmacovigilance"
description: "Patient: {{patient_id}} | Product: {{product_name}} | Event: {{event_description}} | Severity: {{severity}}"
- name: notify-safety-team
type: call
call: msteams.send-message
with:
channel_id: "$secrets.drug_safety_channel"
text: "URGENT: New {{severity}} AE for {{product_name}}. Case: {{create-pv-case.number}}. Patient: {{patient_id}}. Review required within 24 hours."
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Processes environmental monitoring excursions in manufacturing by logging in SAP QM, creating a ServiceNow incident, and alerting quality for Pfizer.
naftiko: "0.5"
info:
label: "Environmental Monitoring Alert Handler"
description: "Processes environmental monitoring excursions in manufacturing by logging in SAP QM, creating a ServiceNow incident, and alerting quality for Pfizer."
tags:
- manufacturing
- quality
- sap
- environmental-monitoring
capability:
exposes:
- type: mcp
namespace: manufacturing-em
port: 8080
tools:
- name: handle-em-excursion
description: "Given environmental excursion details, log a quality notification in SAP, create a ServiceNow incident, and alert quality."
inputParameters:
- name: area_name
in: body
type: string
description: "The monitored area name."
- name: parameter
in: body
type: string
description: "The environmental parameter."
- name: reading
in: body
type: string
description: "The actual reading value."
- name: limit
in: body
type: string
description: "The acceptable limit value."
- name: plant
in: body
type: string
description: "The plant code."
steps:
- name: log-sap-qn
type: call
call: sap.create-quality-notification
with:
notification_type: "Q2"
description: "EM Excursion: {{area_name}} — {{parameter}} reading {{reading}} exceeds limit {{limit}}"
plant: "{{plant}}"
- name: create-snow-incident
type: call
call: servicenow.create-incident
with:
short_description: "EM Excursion: {{area_name}} — {{parameter}}"
category: "environmental_monitoring"
- name: alert-quality
type: call
call: msteams.send-message
with:
channel_id: "$secrets.em_quality_channel"
text: "EM ALERT: {{parameter}} excursion in {{area_name}} at Plant {{plant}}. Reading: {{reading}} (limit: {{limit}}). SAP QN: {{log-sap-qn.notification_number}}. SNOW: {{create-snow-incident.number}}."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_QUALITYNOTIFICATION_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: create-record
method: POST
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Generates FDA inspection readiness checklists by pulling SOPs from SharePoint, checking training compliance in Workday, and creating Jira tracking for Pfizer.
naftiko: "0.5"
info:
label: "FDA Inspection Readiness Checklist Generator"
description: "Generates FDA inspection readiness checklists by pulling SOPs from SharePoint, checking training compliance in Workday, and creating Jira tracking for Pfizer."
tags:
- regulatory
- compliance
- sharepoint
- workday
capability:
exposes:
- type: mcp
namespace: regulatory-compliance
port: 8080
tools:
- name: generate-inspection-checklist
description: "Given a facility and inspection type, compile SOP readiness, training status, and create tracking tasks."
inputParameters:
- name: facility_name
in: body
type: string
description: "The facility being inspected."
- name: inspection_type
in: body
type: string
description: "Type of FDA inspection (pre-approval, routine, for-cause)."
steps:
- name: check-sops
type: call
call: sharepoint.get-document-list
with:
library: "SOPs"
filter: "facility eq '{{facility_name}}'"
- name: check-training
type: call
call: workday.get-training-compliance
with:
facility: "{{facility_name}}"
program: "GMP_Training"
- name: create-epic
type: call
call: jira.create-issue
with:
project: "REG"
summary: "FDA Inspection Readiness: {{facility_name}} — {{inspection_type}}"
issuetype: "Epic"
- name: notify-team
type: call
call: msteams.send-message
with:
channel_id: "$secrets.quality_compliance_channel"
text: "FDA Inspection Readiness for {{facility_name}} ({{inspection_type}}): {{check-sops.count}} SOPs, {{check-training.compliance_rate}}% training compliant. Jira: {{create-epic.key}}."
consumes:
- type: http
namespace: sharepoint
baseUri: "https://pfizer.sharepoint.com/_api/web"
authentication:
type: bearer
token: "$secrets.sharepoint_token"
resources:
- name: lists
path: "/lists"
operations:
- name: get-document-list
method: GET
- type: http
namespace: workday
baseUri: "https://wd5-services1.myworkday.com/ccx/service/pfizer/Learning/v42.0"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: training
path: "/learningAssignments"
operations:
- name: get-training-compliance
method: GET
- type: http
namespace: jira
baseUri: "https://pfizer.atlassian.net/rest/api/3"
authentication:
type: bearer
token: "$secrets.jira_token"
resources:
- name: issues
path: "/issue"
operations:
- name: create-issue
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Triggers GxP validation pipelines in GitHub Actions, logs validation events in ServiceNow, and notifies the QA team for Pfizer.
naftiko: "0.5"
info:
label: "GitHub Actions GxP Validation Pipeline Trigger"
description: "Triggers GxP validation pipelines in GitHub Actions, logs validation events in ServiceNow, and notifies the QA team for Pfizer."
tags:
- devops
- github-actions
- gxp
- validation
capability:
exposes:
- type: mcp
namespace: gxp-devops
port: 8080
tools:
- name: trigger-gxp-validation
description: "Given a system name and validation type, trigger the pipeline, log in ServiceNow, and notify QA."
inputParameters:
- name: repo_name
in: body
type: string
description: "The GitHub repository name."
- name: validation_type
in: body
type: string
description: "Type of validation (IQ, OQ, PQ)."
- name: system_name
in: body
type: string
description: "The GxP system being validated."
steps:
- name: trigger-pipeline
type: call
call: github.trigger-workflow
with:
repo: "{{repo_name}}"
workflow: "gxp-validation.yml"
- name: log-validation
type: call
call: servicenow.create-incident
with:
short_description: "GxP Validation: {{validation_type}} — {{system_name}}"
category: "gxp_validation"
- name: notify-qa
type: call
call: msteams.send-message
with:
channel_id: "$secrets.gxp_qa_channel"
text: "GxP Validation triggered: {{validation_type}} for {{system_name}}. Repo: {{repo_name}}. SNOW: {{log-validation.number}}."
consumes:
- type: http
namespace: github
baseUri: "https://api.github.com"
authentication:
type: bearer
token: "$secrets.github_token"
resources:
- name: workflows
path: "/repos/{{repo}}/actions/workflows/{{workflow}}/dispatches"
inputParameters:
- name: repo
in: path
- name: workflow
in: path
operations:
- name: trigger-workflow
method: POST
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Checks a GitHub repository for branch protection rules and required status checks for Pfizer DevSecOps compliance.
naftiko: "0.5"
info:
label: "GitHub Repository Compliance Check"
description: "Checks a GitHub repository for branch protection rules and required status checks for Pfizer DevSecOps compliance."
tags:
- devops
- github
- compliance
- security
capability:
exposes:
- type: mcp
namespace: devsecops
port: 8080
tools:
- name: check-repo-compliance
description: "Given a repository name, return branch protection status, required reviews count, and CODEOWNERS presence."
inputParameters:
- name: repo_name
in: body
type: string
description: "The GitHub repository name (org/repo format)."
call: github.get-branch-protection
with:
repo_name: "{{repo_name}}"
outputParameters:
- name: protection_enabled
type: boolean
mapping: "$.enabled"
- name: required_reviews
type: integer
mapping: "$.required_pull_request_reviews.required_approving_review_count"
- name: enforce_admins
type: boolean
mapping: "$.enforce_admins.enabled"
consumes:
- type: http
namespace: github
baseUri: "https://api.github.com"
authentication:
type: bearer
token: "$secrets.github_token"
resources:
- name: branch-protection
path: "/repos/{{repo_name}}/branches/main/protection"
inputParameters:
- name: repo_name
in: path
operations:
- name: get-branch-protection
method: GET
Manages GxP-validated system change requests by creating a ServiceNow change, logging in Veeva Vault audit trail, and notifying approvers for Pfizer.
naftiko: "0.5"
info:
label: "GxP System Change Approval Workflow"
description: "Manages GxP-validated system change requests by creating a ServiceNow change, logging in Veeva Vault audit trail, and notifying approvers for Pfizer."
tags:
- compliance
- gxp
- servicenow
- veeva-vault
capability:
exposes:
- type: mcp
namespace: gxp-compliance
port: 8080
tools:
- name: initiate-gxp-change
description: "Given change request details, create a ServiceNow change request, log in Veeva Vault, and notify the CAB."
inputParameters:
- name: system_name
in: body
type: string
description: "Name of the GxP-validated system."
- name: change_description
in: body
type: string
description: "Description of the proposed change."
- name: risk_level
in: body
type: string
description: "Risk classification (low, medium, high, critical)."
steps:
- name: create-change-request
type: call
call: servicenow.create-change
with:
short_description: "GxP Change: {{system_name}} — {{risk_level}} risk"
category: "gxp_change_control"
description: "System: {{system_name}} | Change: {{change_description}} | Risk: {{risk_level}}"
- name: log-vault-audit
type: call
call: veeva.create-object-record
with:
object_type: "change_control__c"
system_name__c: "{{system_name}}"
description__c: "{{change_description}}"
- name: notify-cab
type: call
call: msteams.send-message
with:
channel_id: "$secrets.cab_channel"
text: "GxP Change Request: {{system_name}} ({{risk_level}} risk). SNOW: {{create-change-request.number}}. Vault: {{log-vault-audit.id}}."
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.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: veeva
baseUri: "https://pfizer.veevavault.com/api/v24.1"
authentication:
type: bearer
token: "$secrets.veeva_token"
resources:
- name: object-records
path: "/vobjects/{{object_type}}"
inputParameters:
- name: object_type
in: path
operations:
- name: create-object-record
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Coordinates HCP speaker program events by creating events in Salesforce, logging compliance checks, and notifying medical affairs for Pfizer.
naftiko: "0.5"
info:
label: "HCP Speaker Program Event Coordinator"
description: "Coordinates HCP speaker program events by creating events in Salesforce, logging compliance checks, and notifying medical affairs for Pfizer."
tags:
- medical-affairs
- salesforce
- compliance
- events
capability:
exposes:
- type: mcp
namespace: medical-affairs-events
port: 8080
tools:
- name: coordinate-speaker-event
description: "Given speaker event details, create the event in Salesforce, verify FMV compliance, and notify the team."
inputParameters:
- name: speaker_name
in: body
type: string
description: "Name of the HCP speaker."
- name: event_title
in: body
type: string
description: "Title of the speaker program event."
- name: event_date
in: body
type: string
description: "Date of the event."
- name: honorarium_amount
in: body
type: string
description: "Speaker honorarium amount."
steps:
- name: create-event
type: call
call: salesforce.create-record
with:
object_type: "Speaker_Event__c"
Speaker_Name__c: "{{speaker_name}}"
Event_Title__c: "{{event_title}}"
- name: check-fmv
type: call
call: servicenow.create-incident
with:
short_description: "FMV Compliance Check: {{speaker_name}} — {{honorarium_amount}}"
category: "compliance"
- name: notify-med-affairs
type: call
call: msteams.send-message
with:
channel_id: "$secrets.med_affairs_events_channel"
text: "Speaker Event: {{event_title}} on {{event_date}}. Speaker: {{speaker_name}}. Honorarium: {{honorarium_amount}}. SFDC: {{create-event.id}}. FMV: {{check-fmv.number}}."
consumes:
- type: http
namespace: salesforce
baseUri: "https://pfizer.my.salesforce.com/services/data/v59.0"
authentication:
type: bearer
token: "$secrets.salesforce_token"
resources:
- name: records
path: "/sobjects/Speaker_Event__c"
operations:
- name: create-record
method: POST
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Tracks vulnerability remediation by pulling scan results, creating ServiceNow tickets, and reporting to the CISO dashboard for Pfizer.
naftiko: "0.5"
info:
label: "IT Security Vulnerability Remediation Tracker"
description: "Tracks vulnerability remediation by pulling scan results, creating ServiceNow tickets, and reporting to the CISO dashboard for Pfizer."
tags:
- security
- servicenow
- compliance
- vulnerability-management
capability:
exposes:
- type: mcp
namespace: security-ops
port: 8080
tools:
- name: track-vulnerability-remediation
description: "Given a scan ID and severity threshold, pull results, create remediation tickets, and update the dashboard."
inputParameters:
- name: scan_id
in: body
type: string
description: "The vulnerability scan identifier."
- name: severity_threshold
in: body
type: string
description: "Minimum severity to track (critical, high, medium)."
steps:
- name: get-findings
type: call
call: servicenow.get-vulnerabilities
with:
scan_id: "{{scan_id}}"
severity: "{{severity_threshold}}"
- name: create-tickets
type: call
call: servicenow.create-incident
with:
short_description: "Vulnerability Remediation: Scan {{scan_id}}"
category: "security"
- name: notify-security
type: call
call: msteams.send-message
with:
channel_id: "$secrets.security_ops_channel"
text: "Vulnerability Scan {{scan_id}}: {{get-findings.count}} findings at {{severity_threshold}}+ severity. Ticket: {{create-tickets.number}}."
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves the status and details of a Jira issue by key for Pfizer clinical operations project tracking.
naftiko: "0.5"
info:
label: "Jira Clinical Issue Status Lookup"
description: "Retrieves the status and details of a Jira issue by key for Pfizer clinical operations project tracking."
tags:
- clinical-trials
- jira
- project-management
- lookup
capability:
exposes:
- type: mcp
namespace: clinical-pm
port: 8080
tools:
- name: get-issue-status
description: "Given a Jira issue key, return the issue summary, status, assignee, and priority."
inputParameters:
- name: issue_key
in: body
type: string
description: "The Jira issue key (e.g., CLIN-1234)."
call: jira.get-issue
with:
issue_key: "{{issue_key}}"
outputParameters:
- name: summary
type: string
mapping: "$.fields.summary"
- name: status
type: string
mapping: "$.fields.status.name"
- name: assignee
type: string
mapping: "$.fields.assignee.displayName"
- name: priority
type: string
mapping: "$.fields.priority.name"
consumes:
- type: http
namespace: jira
baseUri: "https://pfizer.atlassian.net/rest/api/3"
authentication:
type: bearer
token: "$secrets.jira_token"
resources:
- name: issues
path: "/issue/{{issue_key}}"
inputParameters:
- name: issue_key
in: path
operations:
- name: get-issue
method: GET
Tracks laboratory instrument calibration schedules by querying SAP PM, creating ServiceNow work orders, and notifying lab managers for Pfizer.
naftiko: "0.5"
info:
label: "Laboratory Instrument Calibration Tracker"
description: "Tracks laboratory instrument calibration schedules by querying SAP PM, creating ServiceNow work orders, and notifying lab managers for Pfizer."
tags:
- r-and-d
- quality
- sap
- laboratory
capability:
exposes:
- type: mcp
namespace: lab-ops
port: 8080
tools:
- name: track-calibration
description: "Given a lab identifier, find instruments due for calibration, create work orders, and notify lab management."
inputParameters:
- name: lab_id
in: body
type: string
description: "The laboratory identifier."
- name: days_ahead
in: body
type: integer
description: "Days ahead to check for calibration due dates."
steps:
- name: query-instruments
type: call
call: sap.get-equipment-list
with:
lab_id: "{{lab_id}}"
next_calibration_within: "{{days_ahead}}"
- name: create-work-orders
type: call
call: servicenow.create-incident
with:
short_description: "Lab Calibration Due: {{query-instruments.count}} instruments in Lab {{lab_id}}"
category: "lab_operations"
- name: notify-lab-manager
type: call
call: msteams.send-message
with:
channel_id: "$secrets.lab_ops_channel"
text: "Calibration Alert: {{query-instruments.count}} instruments in Lab {{lab_id}} due within {{days_ahead}} days. SNOW: {{create-work-orders.number}}."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_EQUIPMENT_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: create-record
method: POST
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Fetches LinkedIn company page engagement metrics relevant to medical affairs content and posts a bi-weekly digest to the medical affairs communications Teams channel.
naftiko: "0.5"
info:
label: "LinkedIn Medical Affairs Engagement Digest"
description: "Fetches LinkedIn company page engagement metrics relevant to medical affairs content and posts a bi-weekly digest to the medical affairs communications Teams channel."
tags:
- marketing
- linkedin
- social
- medical-affairs
- reporting
- microsoft-teams
capability:
exposes:
- type: mcp
namespace: medaffairs-reporting
port: 8080
tools:
- name: digest-linkedin-engagement
description: "Retrieve LinkedIn organization page share statistics for the past 30 days and post a medical affairs engagement digest to the communications Teams channel."
inputParameters:
- name: organization_id
in: body
type: string
description: "The LinkedIn organization ID for Pfizer's company page."
- name: teams_channel_id
in: body
type: string
description: "Teams channel ID for the medical affairs communications team."
steps:
- name: get-engagement
type: call
call: linkedin.get-share-statistics
with:
organization_id: "{{organization_id}}"
- name: post-digest
type: call
call: msteams.send-message
with:
channel_id: "{{teams_channel_id}}"
text: "LinkedIn Engagement (30d): Impressions: {{get-engagement.impressions}} | Reactions: {{get-engagement.likes}} | Shares: {{get-engagement.shares}} | Follower Growth: +{{get-engagement.follower_gain}}"
consumes:
- type: http
namespace: linkedin
baseUri: "https://api.linkedin.com/v2"
authentication:
type: bearer
token: "$secrets.linkedin_token"
resources:
- name: share-statistics
path: "/organizationalEntityShareStatistics"
inputParameters:
- name: organization_id
in: query
operations:
- name: get-share-statistics
method: GET
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Sources MSL candidates from LinkedIn, creates profiles in Workday recruiting, and notifies the talent acquisition team for Pfizer.
naftiko: "0.5"
info:
label: "LinkedIn Talent Pipeline for Medical Science Liaisons"
description: "Sources MSL candidates from LinkedIn, creates profiles in Workday recruiting, and notifies the talent acquisition team for Pfizer."
tags:
- hr
- linkedin
- workday
- talent-acquisition
capability:
exposes:
- type: mcp
namespace: hr-talent-sourcing
port: 8080
tools:
- name: source-msl-candidates
description: "Given search criteria for MSL roles, source candidates from LinkedIn, create prospects in Workday, and notify TA."
inputParameters:
- name: therapeutic_area
in: body
type: string
description: "The target therapeutic area."
- name: location
in: body
type: string
description: "The target geographic location."
- name: experience_years
in: body
type: integer
description: "Minimum years of experience."
steps:
- name: search-linkedin
type: call
call: linkedin.search-candidates
with:
keywords: "Medical Science Liaison {{therapeutic_area}}"
location: "{{location}}"
- name: create-prospects
type: call
call: workday.create-prospect
with:
source: "LinkedIn"
requisition_area: "{{therapeutic_area}}"
- name: notify-ta
type: call
call: msteams.send-message
with:
channel_id: "$secrets.talent_channel"
text: "MSL Talent Pipeline: {{search-linkedin.count}} candidates found for {{therapeutic_area}} in {{location}}."
consumes:
- type: http
namespace: linkedin
baseUri: "https://api.linkedin.com/v2"
authentication:
type: bearer
token: "$secrets.linkedin_token"
resources:
- name: people-search
path: "/people?keywords={{keywords}}"
inputParameters:
- name: keywords
in: query
operations:
- name: search-candidates
method: GET
- type: http
namespace: workday
baseUri: "https://wd5-services1.myworkday.com/ccx/service/pfizer/Recruiting/v42.0"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: prospects
path: "/prospects"
operations:
- name: create-prospect
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Processes manufacturing deviations by creating a ServiceNow incident, logging in SAP QM, and notifying quality assurance for Pfizer.
naftiko: "0.5"
info:
label: "Manufacturing Deviation Handler"
description: "Processes manufacturing deviations by creating a ServiceNow incident, logging in SAP QM, and notifying quality assurance for Pfizer."
tags:
- manufacturing
- quality
- servicenow
- sap
capability:
exposes:
- type: mcp
namespace: manufacturing-qa
port: 8080
tools:
- name: handle-deviation
description: "Given deviation details, create a ServiceNow incident, log in SAP quality management, and notify the QA team."
inputParameters:
- name: batch_number
in: body
type: string
description: "The manufacturing batch number."
- name: deviation_type
in: body
type: string
description: "Type of deviation (process, equipment, material)."
- name: description
in: body
type: string
description: "Detailed description of the deviation."
- name: plant
in: body
type: string
description: "The manufacturing plant code."
steps:
- name: create-snow-incident
type: call
call: servicenow.create-incident
with:
short_description: "MFG Deviation: {{deviation_type}} — Batch {{batch_number}}"
category: "manufacturing_quality"
description: "Plant: {{plant}} | Batch: {{batch_number}} | Type: {{deviation_type}} | Details: {{description}}"
- name: log-sap-notification
type: call
call: sap.create-quality-notification
with:
notification_type: "Q2"
material: "{{batch_number}}"
plant: "{{plant}}"
description: "{{deviation_type}}: {{description}}"
- name: notify-qa
type: call
call: msteams.send-message
with:
channel_id: "$secrets.qa_channel"
text: "MFG Deviation Alert: {{deviation_type}} at Plant {{plant}}, Batch {{batch_number}}. SNOW: {{create-snow-incident.number}}. SAP QN: {{log-sap-notification.notification_number}}."
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.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: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_QUALITYNOTIFICATION_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: create-record
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Processes medical information requests by logging in Salesforce, searching the knowledge base, and notifying the medical affairs team for Pfizer.
naftiko: "0.5"
info:
label: "Medical Information Request Handler"
description: "Processes medical information requests by logging in Salesforce, searching the knowledge base, and notifying the medical affairs team for Pfizer."
tags:
- medical-affairs
- salesforce
- knowledge-management
- compliance
capability:
exposes:
- type: mcp
namespace: medical-affairs
port: 8080
tools:
- name: handle-med-info-request
description: "Given a medical information request, log in Salesforce, search the knowledge base, and notify medical affairs."
inputParameters:
- name: requestor_name
in: body
type: string
description: "Name of the healthcare professional."
- name: product_name
in: body
type: string
description: "The product being inquired about."
- name: question
in: body
type: string
description: "The medical information question."
- name: channel
in: body
type: string
description: "Request channel (phone, email, web)."
steps:
- name: log-in-salesforce
type: call
call: salesforce.create-case
with:
subject: "MedInfo Request: {{product_name}}"
description: "Requestor: {{requestor_name}} | Product: {{product_name}} | Question: {{question}}"
type: "Medical_Information"
- name: search-knowledge
type: call
call: confluence.search-content
with:
search_query: "{{product_name}} {{question}}"
- name: notify-med-affairs
type: call
call: msteams.send-message
with:
channel_id: "$secrets.med_affairs_channel"
text: "New MedInfo Request from {{requestor_name}} about {{product_name}}. Case: {{log-in-salesforce.id}}. KB matches: {{search-knowledge.totalSize}}."
consumes:
- type: http
namespace: salesforce
baseUri: "https://pfizer.my.salesforce.com/services/data/v59.0"
authentication:
type: bearer
token: "$secrets.salesforce_token"
resources:
- name: cases
path: "/sobjects/Case"
operations:
- name: create-case
method: POST
- type: http
namespace: confluence
baseUri: "https://pfizer.atlassian.net/wiki/rest/api"
authentication:
type: bearer
token: "$secrets.confluence_token"
resources:
- name: search
path: "/content/search"
operations:
- name: search-content
method: GET
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Launches periodic access certification campaigns by pulling user data from Okta, creating review tasks, and notifying managers for Pfizer.
naftiko: "0.5"
info:
label: "Okta Access Certification Campaign Launcher"
description: "Launches periodic access certification campaigns by pulling user data from Okta, creating review tasks, and notifying managers for Pfizer."
tags:
- security
- okta
- servicenow
- compliance
capability:
exposes:
- type: mcp
namespace: identity-governance
port: 8080
tools:
- name: launch-access-certification
description: "Given a certification scope, pull active users from Okta, create review tasks, and notify owners."
inputParameters:
- name: application_name
in: body
type: string
description: "The Okta application name to certify."
- name: campaign_name
in: body
type: string
description: "The certification campaign name."
steps:
- name: get-users
type: call
call: okta.get-app-users
with:
application_name: "{{application_name}}"
- name: create-campaign
type: call
call: servicenow.create-incident
with:
short_description: "Access Certification: {{campaign_name}} — {{application_name}}"
category: "identity_governance"
- name: notify-owners
type: call
call: msteams.send-message
with:
channel_id: "$secrets.iam_channel"
text: "Access Certification: {{campaign_name}} for {{application_name}}. {{get-users.count}} users to review. SNOW: {{create-campaign.number}}."
consumes:
- type: http
namespace: okta
baseUri: "https://pfizer.okta.com/api/v1"
authentication:
type: bearer
token: "$secrets.okta_token"
resources:
- name: app-users
path: "/apps/{{application_name}}/users"
inputParameters:
- name: application_name
in: path
operations:
- name: get-app-users
method: GET
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Lists Okta users assigned to privileged application groups and creates a ServiceNow security task for the quarterly access review process.
naftiko: "0.5"
info:
label: "Okta Privileged Access Review"
description: "Lists Okta users assigned to privileged application groups and creates a ServiceNow security task for the quarterly access review process."
tags:
- security
- identity
- okta
- servicenow
- access-review
- compliance
capability:
exposes:
- type: mcp
namespace: access-review
port: 8080
tools:
- name: run-privileged-access-review
description: "Given an Okta privileged group ID and review quarter label, list all members and create a ServiceNow access review task for the security team to certify."
inputParameters:
- name: okta_group_id
in: body
type: string
description: "The Okta privileged access group ID to audit."
- name: review_quarter
in: body
type: string
description: "The review period label (e.g., 'Q2-2026')."
steps:
- name: list-privileged-users
type: call
call: okta.list-group-members
with:
group_id: "{{okta_group_id}}"
- name: create-review-task
type: call
call: servicenow.create-incident
with:
short_description: "Privileged Access Review — {{review_quarter}} — Group {{okta_group_id}}"
category: "security_access_review"
description: "{{list-privileged-users.count}} privileged users require certification. User list: {{list-privileged-users.emails}}"
consumes:
- type: http
namespace: okta
baseUri: "https://pfizer.okta.com/api/v1"
authentication:
type: apikey
key: "Authorization"
value: "$secrets.okta_api_key"
placement: header
resources:
- name: group-members
path: "/groups/{{group_id}}/users"
inputParameters:
- name: group_id
in: path
operations:
- name: list-group-members
method: GET
- type: http
namespace: servicenow
baseUri: "https://pfizer.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
Retrieves the current status and profile of an Okta user by login email for Pfizer identity management.
naftiko: "0.5"
info:
label: "Okta User Status Lookup"
description: "Retrieves the current status and profile of an Okta user by login email for Pfizer identity management."
tags:
- security
- okta
- identity
- lookup
capability:
exposes:
- type: mcp
namespace: identity-ops
port: 8080
tools:
- name: get-user-status
description: "Given a user email, return the Okta user status, last login, and MFA enrollment status."
inputParameters:
- name: user_email
in: body
type: string
description: "The user login email address."
call: okta.get-user
with:
user_email: "{{user_email}}"
outputParameters:
- name: status
type: string
mapping: "$.status"
- name: last_login
type: string
mapping: "$.lastLogin"
- name: mfa_enrolled
type: boolean
mapping: "$.credentials.provider.type"
consumes:
- type: http
namespace: okta
baseUri: "https://pfizer.okta.com/api/v1"
authentication:
type: bearer
token: "$secrets.okta_token"
resources:
- name: users
path: "/users/{{user_email}}"
inputParameters:
- name: user_email
in: path
operations:
- name: get-user
method: GET
When a P1 production incident is declared, creates a ServiceNow P1 incident, annotates Datadog, and alerts the engineering on-call team in Microsoft Teams.
naftiko: "0.5"
info:
label: "P1 Production Incident Response"
description: "When a P1 production incident is declared, creates a ServiceNow P1 incident, annotates Datadog, and alerts the engineering on-call team in Microsoft Teams."
tags:
- itsm
- incident-response
- servicenow
- datadog
- microsoft-teams
capability:
exposes:
- type: mcp
namespace: itsm-ops
port: 8080
tools:
- name: handle-p1-incident
description: "Given an affected system and impact description, create a ServiceNow P1 incident, create a Datadog event, and send an urgent Teams alert to the engineering team."
inputParameters:
- name: affected_system
in: body
type: string
description: "The Pfizer system or service experiencing the P1 incident."
- name: impact_description
in: body
type: string
description: "Brief description of the business impact and affected users."
- name: teams_channel_id
in: body
type: string
description: "Teams channel ID for the engineering on-call alert."
steps:
- name: create-p1-incident
type: call
call: servicenow.create-incident
with:
short_description: "P1: {{affected_system}} — {{impact_description}}"
urgency: "1"
priority: "1"
category: "application"
- name: create-dd-event
type: call
call: datadog.create-event
with:
title: "P1 Incident: {{affected_system}}"
text: "SNOW {{create-p1-incident.number}} — {{impact_description}}"
alert_type: "error"
- name: alert-oncall
type: call
call: msteams.send-message
with:
channel_id: "{{teams_channel_id}}"
text: "P1 INCIDENT DECLARED: {{affected_system}} | Impact: {{impact_description}} | SNOW: {{create-p1-incident.number}} | Datadog: {{create-dd-event.url}}"
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.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: datadog
baseUri: "https://api.datadoghq.com/api/v1"
authentication:
type: apikey
key: "DD-API-KEY"
value: "$secrets.datadog_api_key"
placement: header
resources:
- name: events
path: "/events"
operations:
- name: create-event
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Processes patient assistance program enrollments by creating cases in Salesforce, verifying eligibility, and notifying patient services for Pfizer.
naftiko: "0.5"
info:
label: "Patient Assistance Program Enrollment Processor"
description: "Processes patient assistance program enrollments by creating cases in Salesforce, verifying eligibility, and notifying patient services for Pfizer."
tags:
- commercial
- salesforce
- patient-services
- compliance
capability:
exposes:
- type: mcp
namespace: patient-services
port: 8080
tools:
- name: process-pap-enrollment
description: "Given patient enrollment details, create a Salesforce case, verify eligibility, and notify the patient services team."
inputParameters:
- name: patient_id
in: body
type: string
description: "The patient identifier."
- name: product_name
in: body
type: string
description: "The product for which assistance is requested."
- name: insurance_status
in: body
type: string
description: "Patient insurance status."
steps:
- name: create-case
type: call
call: salesforce.create-case
with:
subject: "PAP Enrollment: {{product_name}} — Patient {{patient_id}}"
type: "Patient_Assistance"
- name: verify-eligibility
type: call
call: snowflake.execute-query
with:
statement: "SELECT eligible FROM pap_eligibility_rules WHERE product = '{{product_name}}'"
warehouse: "COMMERCIAL_WH"
- name: notify-team
type: call
call: msteams.send-message
with:
channel_id: "$secrets.patient_services_channel"
text: "PAP Enrollment: Patient {{patient_id}} for {{product_name}}. Eligibility: {{verify-eligibility.data}}. Case: {{create-case.id}}."
consumes:
- type: http
namespace: salesforce
baseUri: "https://pfizer.my.salesforce.com/services/data/v59.0"
authentication:
type: bearer
token: "$secrets.salesforce_token"
resources:
- name: cases
path: "/sobjects/Case"
operations:
- name: create-case
method: POST
- type: http
namespace: snowflake
baseUri: "https://pfizer.snowflakecomputing.com/api/v2"
authentication:
type: bearer
token: "$secrets.snowflake_token"
resources:
- name: statements
path: "/statements"
operations:
- name: execute-query
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Runs pharmacovigilance signal detection queries in Snowflake, generates summary reports, and alerts the safety review board for Pfizer.
naftiko: "0.5"
info:
label: "Pharmacovigilance Signal Detection Reporter"
description: "Runs pharmacovigilance signal detection queries in Snowflake, generates summary reports, and alerts the safety review board for Pfizer."
tags:
- drug-safety
- pharmacovigilance
- snowflake
- analytics
capability:
exposes:
- type: mcp
namespace: pv-analytics
port: 8080
tools:
- name: run-signal-detection
description: "Given a product and time period, run signal detection queries, create a Jira tracking issue, and alert the safety board."
inputParameters:
- name: product_name
in: body
type: string
description: "The drug product name."
- name: period_start
in: body
type: string
description: "Analysis period start date."
- name: period_end
in: body
type: string
description: "Analysis period end date."
steps:
- name: run-detection
type: call
call: snowflake.execute-query
with:
statement: "CALL pv_signal_detection('{{product_name}}', '{{period_start}}', '{{period_end}}')"
warehouse: "PV_WH"
- name: create-review-ticket
type: call
call: jira.create-issue
with:
project: "PV"
summary: "Signal Detection: {{product_name}} ({{period_start}} to {{period_end}})"
issuetype: "Task"
- name: alert-safety-board
type: call
call: msteams.send-message
with:
channel_id: "$secrets.safety_board_channel"
text: "PV Signal Detection: {{product_name}} ({{period_start}} to {{period_end}}). Signals: {{run-detection.signal_count}}. Jira: {{create-review-ticket.key}}."
consumes:
- type: http
namespace: snowflake
baseUri: "https://pfizer.snowflakecomputing.com/api/v2"
authentication:
type: bearer
token: "$secrets.snowflake_token"
resources:
- name: statements
path: "/statements"
operations:
- name: execute-query
method: POST
- type: http
namespace: jira
baseUri: "https://pfizer.atlassian.net/rest/api/3"
authentication:
type: bearer
token: "$secrets.jira_token"
resources:
- name: issues
path: "/issue"
operations:
- name: create-issue
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Checks the last refresh status of a Power BI dataset for Pfizer analytics operations.
naftiko: "0.5"
info:
label: "Power BI Dataset Refresh Status"
description: "Checks the last refresh status of a Power BI dataset for Pfizer analytics operations."
tags:
- analytics
- power-bi
- reporting
- lookup
capability:
exposes:
- type: mcp
namespace: analytics-ops
port: 8080
tools:
- name: get-refresh-status
description: "Given a Power BI dataset ID, return the last refresh status, start time, and end time."
inputParameters:
- name: dataset_id
in: body
type: string
description: "The Power BI dataset ID."
call: powerbi.get-refresh-history
with:
dataset_id: "{{dataset_id}}"
outputParameters:
- name: status
type: string
mapping: "$.value[0].status"
- name: start_time
type: string
mapping: "$.value[0].startTime"
- name: end_time
type: string
mapping: "$.value[0].endTime"
consumes:
- type: http
namespace: powerbi
baseUri: "https://api.powerbi.com/v1.0/myorg"
authentication:
type: bearer
token: "$secrets.powerbi_token"
resources:
- name: datasets
path: "/datasets/{{dataset_id}}/refreshes?$top=1"
inputParameters:
- name: dataset_id
in: path
operations:
- name: get-refresh-history
method: GET
Triggers a Power BI dataset refresh for the global financial reporting dashboard and notifies the finance team in Microsoft Teams.
naftiko: "0.5"
info:
label: "Power BI Financial Reporting Refresh"
description: "Triggers a Power BI dataset refresh for the global financial reporting dashboard and notifies the finance team in Microsoft Teams."
tags:
- data
- analytics
- power-bi
- finance
- microsoft-teams
- reporting
capability:
exposes:
- type: mcp
namespace: finance-bi
port: 8080
tools:
- name: refresh-financial-dashboard
description: "Trigger a Power BI refresh for the Pfizer global financial dashboard and notify the finance team in Teams upon initiation."
inputParameters:
- name: dataset_id
in: body
type: string
description: "The Power BI dataset ID for the global financial dashboard."
- name: teams_channel_id
in: body
type: string
description: "Teams channel ID to notify the finance team."
steps:
- name: trigger-refresh
type: call
call: powerbi.refresh-dataset
with:
dataset_id: "{{dataset_id}}"
- name: notify-finance
type: call
call: msteams.send-message
with:
channel_id: "{{teams_channel_id}}"
text: "Financial dashboard refresh initiated. Dataset: {{dataset_id}}. Status: {{trigger-refresh.status}}."
consumes:
- type: http
namespace: powerbi
baseUri: "https://api.powerbi.com/v1.0/myorg"
authentication:
type: bearer
token: "$secrets.powerbi_token"
resources:
- name: refreshes
path: "/datasets/{{dataset_id}}/refreshes"
inputParameters:
- name: dataset_id
in: path
operations:
- name: refresh-dataset
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Coordinates product recall activities by creating cases in Salesforce, notifying logistics via SAP, and alerting leadership for Pfizer.
naftiko: "0.5"
info:
label: "Product Recall Coordination Workflow"
description: "Coordinates product recall activities by creating cases in Salesforce, notifying logistics via SAP, and alerting leadership for Pfizer."
tags:
- quality
- product-recall
- salesforce
- sap
capability:
exposes:
- type: mcp
namespace: quality-recall
port: 8080
tools:
- name: initiate-recall
description: "Given product recall details, create a Salesforce case, update SAP batch status, and send urgent notifications."
inputParameters:
- name: product_name
in: body
type: string
description: "The product name being recalled."
- name: batch_numbers
in: body
type: string
description: "Comma-separated affected batch numbers."
- name: recall_reason
in: body
type: string
description: "Reason for the recall."
- name: recall_class
in: body
type: string
description: "Recall classification (Class I, II, III)."
steps:
- name: create-recall-case
type: call
call: salesforce.create-case
with:
subject: "Product Recall: {{product_name}} — {{recall_class}}"
type: "Product_Recall"
- name: update-batch-status
type: call
call: sap.update-batch-status
with:
batch_numbers: "{{batch_numbers}}"
status: "blocked"
- name: alert-leadership
type: call
call: msteams.send-message
with:
channel_id: "$secrets.executive_channel"
text: "URGENT — Product Recall: {{product_name}} ({{recall_class}}). Batches: {{batch_numbers}}. Case: {{create-recall-case.id}}."
consumes:
- type: http
namespace: salesforce
baseUri: "https://pfizer.my.salesforce.com/services/data/v59.0"
authentication:
type: bearer
token: "$secrets.salesforce_token"
resources:
- name: cases
path: "/sobjects/Case"
operations:
- name: create-case
method: POST
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_BATCH_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: create-record
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Refreshes the R&D pipeline dashboard by pulling compound status from Snowflake, updating Power BI, and notifying R&D leadership for Pfizer.
naftiko: "0.5"
info:
label: "R&D Compound Pipeline Dashboard Refresh"
description: "Refreshes the R&D pipeline dashboard by pulling compound status from Snowflake, updating Power BI, and notifying R&D leadership for Pfizer."
tags:
- r-and-d
- snowflake
- power-bi
- analytics
capability:
exposes:
- type: mcp
namespace: rd-analytics
port: 8080
tools:
- name: refresh-pipeline-dashboard
description: "Trigger a pipeline data extract from Snowflake, refresh the Power BI dataset, and notify leadership."
inputParameters:
- name: dashboard_id
in: body
type: string
description: "The Power BI dashboard dataset ID."
- name: teams_channel_id
in: body
type: string
description: "Teams channel for R&D leadership."
steps:
- name: extract-pipeline-data
type: call
call: snowflake.execute-query
with:
statement: "CALL refresh_rd_pipeline_snapshot()"
warehouse: "RD_WH"
- name: refresh-powerbi
type: call
call: powerbi.trigger-refresh
with:
dataset_id: "{{dashboard_id}}"
- name: notify-leadership
type: call
call: msteams.send-message
with:
channel_id: "{{teams_channel_id}}"
text: "R&D Pipeline Dashboard refreshed. Data as of {{extract-pipeline-data.timestamp}}."
consumes:
- type: http
namespace: snowflake
baseUri: "https://pfizer.snowflakecomputing.com/api/v2"
authentication:
type: bearer
token: "$secrets.snowflake_token"
resources:
- name: statements
path: "/statements"
operations:
- name: execute-query
method: POST
- type: http
namespace: powerbi
baseUri: "https://api.powerbi.com/v1.0/myorg"
authentication:
type: bearer
token: "$secrets.powerbi_token"
resources:
- name: datasets
path: "/datasets/{{dataset_id}}/refreshes"
inputParameters:
- name: dataset_id
in: path
operations:
- name: trigger-refresh
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Orchestrates RWE data ingestion from external sources into Snowflake, validates data quality, and notifies the HEOR team for Pfizer.
naftiko: "0.5"
info:
label: "Real-World Evidence Data Ingestion Pipeline"
description: "Orchestrates RWE data ingestion from external sources into Snowflake, validates data quality, and notifies the HEOR team for Pfizer."
tags:
- r-and-d
- real-world-evidence
- snowflake
- data-engineering
capability:
exposes:
- type: mcp
namespace: rwe-analytics
port: 8080
tools:
- name: ingest-rwe-data
description: "Given a data source and dataset identifier, ingest into Snowflake, run quality checks, and notify HEOR."
inputParameters:
- name: data_source
in: body
type: string
description: "The RWE data source name (claims, EMR, registry)."
- name: dataset_id
in: body
type: string
description: "The dataset identifier."
- name: study_id
in: body
type: string
description: "The associated study ID."
steps:
- name: ingest-data
type: call
call: snowflake.execute-query
with:
statement: "CALL rwe_ingest_pipeline('{{data_source}}', '{{dataset_id}}', '{{study_id}}')"
warehouse: "RWE_WH"
- name: validate-quality
type: call
call: snowflake.execute-query
with:
statement: "CALL rwe_data_quality_check('{{dataset_id}}')"
warehouse: "RWE_WH"
- name: notify-heor
type: call
call: msteams.send-message
with:
channel_id: "$secrets.heor_channel"
text: "RWE Data Ingestion Complete: {{data_source}} ({{dataset_id}}) for Study {{study_id}}. Records: {{ingest-data.row_count}}."
consumes:
- type: http
namespace: snowflake
baseUri: "https://pfizer.snowflakecomputing.com/api/v2"
authentication:
type: bearer
token: "$secrets.snowflake_token"
resources:
- name: statements
path: "/statements"
operations:
- name: execute-query
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Queries Veeva Vault for upcoming regulatory submission deadlines, creates Jira tracking tickets, and alerts the regulatory affairs team for Pfizer.
naftiko: "0.5"
info:
label: "Regulatory Submission Deadline Tracker"
description: "Queries Veeva Vault for upcoming regulatory submission deadlines, creates Jira tracking tickets, and alerts the regulatory affairs team for Pfizer."
tags:
- regulatory
- veeva-vault
- jira
- compliance
capability:
exposes:
- type: mcp
namespace: regulatory-ops
port: 8080
tools:
- name: track-submission-deadlines
description: "Given a time horizon in days, find upcoming submission deadlines, create Jira tickets, and post a summary."
inputParameters:
- name: days_ahead
in: body
type: integer
description: "Number of days ahead to check for deadlines."
- name: teams_channel_id
in: body
type: string
description: "Teams channel for regulatory affairs notifications."
steps:
- name: query-deadlines
type: call
call: veeva.query-submissions
with:
query: "SELECT id, name__v, submission_date__c FROM submission__c WHERE submission_date__c <= DATEADD(day,{{days_ahead}},GETDATE())"
- name: create-tracker
type: call
call: jira.create-issue
with:
project: "REG"
summary: "Upcoming Submissions: {{query-deadlines.totalCount}} items within {{days_ahead}} days"
issuetype: "Task"
- name: alert-team
type: call
call: msteams.send-message
with:
channel_id: "{{teams_channel_id}}"
text: "Regulatory Alert: {{query-deadlines.totalCount}} submissions due within {{days_ahead}} days. Jira: {{create-tracker.key}}"
consumes:
- type: http
namespace: veeva
baseUri: "https://pfizer.veevavault.com/api/v24.1"
authentication:
type: bearer
token: "$secrets.veeva_token"
resources:
- name: object-records
path: "/vobjects/{{object_type}}"
inputParameters:
- name: object_type
in: path
operations:
- name: create-object-record
method: POST
- type: http
namespace: jira
baseUri: "https://pfizer.atlassian.net/rest/api/3"
authentication:
type: bearer
token: "$secrets.jira_token"
resources:
- name: issues
path: "/issue"
operations:
- name: create-issue
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves a regulatory document from SharePoint and uses Anthropic Claude to generate a concise regulatory affairs summary, posting the result to the regulatory team's Teams channel.
naftiko: "0.5"
info:
label: "Regulatory Submission Document Summary"
description: "Retrieves a regulatory document from SharePoint and uses Anthropic Claude to generate a concise regulatory affairs summary, posting the result to the regulatory team's Teams channel."
tags:
- regulatory
- ai
- anthropic
- sharepoint
- microsoft-teams
- compliance
capability:
exposes:
- type: mcp
namespace: regulatory-ai
port: 8080
tools:
- name: summarize-regulatory-document
description: "Given a SharePoint document URL and regulatory context (e.g., IND, NDA, BLA), retrieve the document content and generate an AI regulatory affairs summary via Anthropic Claude."
inputParameters:
- name: document_id
in: body
type: string
description: "The SharePoint document item ID to summarize."
- name: site_id
in: body
type: string
description: "The SharePoint site ID containing the regulatory document."
- name: regulatory_context
in: body
type: string
description: "The regulatory submission context (e.g., 'IND', 'NDA', 'BLA', 'MAA')."
- name: teams_channel_id
in: body
type: string
description: "Teams channel ID for the regulatory affairs team."
steps:
- name: get-document
type: call
call: sharepoint.get-file-content
with:
site_id: "{{site_id}}"
document_id: "{{document_id}}"
- name: generate-summary
type: call
call: anthropic.create-message
with:
model: "claude-3-5-sonnet-20241022"
prompt: "You are a regulatory affairs expert at a pharmaceutical company. Summarize the following {{regulatory_context}} document in 5 bullet points highlighting key regulatory implications, data requirements, and action items: {{get-document.content}}"
- name: post-summary
type: call
call: msteams.send-message
with:
channel_id: "{{teams_channel_id}}"
text: "Regulatory Summary ({{regulatory_context}}) — {{get-document.name}}:\n{{generate-summary.content}}"
consumes:
- type: http
namespace: sharepoint
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.sharepoint_token"
resources:
- name: files
path: "/sites/{{site_id}}/drive/items/{{document_id}}/content"
inputParameters:
- name: site_id
in: path
- name: document_id
in: path
operations:
- name: get-file-content
method: GET
- type: http
namespace: anthropic
baseUri: "https://api.anthropic.com/v1"
authentication:
type: apikey
key: "x-api-key"
value: "$secrets.anthropic_api_key"
placement: header
resources:
- name: messages
path: "/messages"
operations:
- name: create-message
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Queries Salesforce for open commercial opportunities by therapeutic area and posts a pipeline digest to the commercial operations Microsoft Teams channel.
naftiko: "0.5"
info:
label: "Salesforce Commercial Opportunity Pipeline Digest"
description: "Queries Salesforce for open commercial opportunities by therapeutic area and posts a pipeline digest to the commercial operations Microsoft Teams channel."
tags:
- sales
- crm
- salesforce
- reporting
- microsoft-teams
- commercial
capability:
exposes:
- type: mcp
namespace: commercial-reporting
port: 8080
tools:
- name: digest-pipeline
description: "Given a Salesforce therapeutic area field value and Teams channel, query open opportunities and post a commercial pipeline digest."
inputParameters:
- name: therapeutic_area
in: body
type: string
description: "The therapeutic area to filter opportunities (e.g., 'Oncology', 'Immunology', 'Rare Disease')."
- name: teams_channel_id
in: body
type: string
description: "Teams channel ID for the commercial pipeline digest."
steps:
- name: query-opportunities
type: call
call: salesforce.query-records
with:
q: "SELECT Id,Name,StageName,Amount,CloseDate FROM Opportunity WHERE Therapeutic_Area__c = '{{therapeutic_area}}' AND IsClosed = false"
- name: post-digest
type: call
call: msteams.send-message
with:
channel_id: "{{teams_channel_id}}"
text: "Pipeline Digest — {{therapeutic_area}}: {{query-opportunities.totalSize}} open opportunities | Total pipeline: ${{query-opportunities.total_amount}}"
consumes:
- type: http
namespace: salesforce
baseUri: "https://pfizer.my.salesforce.com/services/data/v58.0"
authentication:
type: bearer
token: "$secrets.salesforce_token"
resources:
- name: query
path: "/query"
inputParameters:
- name: q
in: query
operations:
- name: query-records
method: GET
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Orchestrates commercial territory realignment by updating Salesforce territories, adjusting Workday reporting, and notifying the commercial team for Pfizer.
naftiko: "0.5"
info:
label: "Salesforce Commercial Territory Realignment Orchestrator"
description: "Orchestrates commercial territory realignment by updating Salesforce territories, adjusting Workday reporting, and notifying the commercial team for Pfizer."
tags:
- commercial
- salesforce
- workday
- territory-management
capability:
exposes:
- type: mcp
namespace: commercial-ops-mgmt
port: 8080
tools:
- name: realign-territories
description: "Given territory changes, update Salesforce assignments, adjust Workday structures, and notify the team."
inputParameters:
- name: territory_id
in: body
type: string
description: "The territory identifier."
- name: new_rep_id
in: body
type: string
description: "The new sales representative employee ID."
- name: effective_date
in: body
type: string
description: "Effective date of the realignment."
steps:
- name: update-salesforce
type: call
call: salesforce.update-record
with:
object_type: "Territory2"
id: "{{territory_id}}"
Assigned_Rep__c: "{{new_rep_id}}"
- name: update-workday
type: call
call: workday.update-assignment
with:
employee_id: "{{new_rep_id}}"
territory: "{{territory_id}}"
- name: notify-commercial
type: call
call: msteams.send-message
with:
channel_id: "$secrets.commercial_ops_channel"
text: "Territory Realignment: Territory {{territory_id}} assigned to Rep {{new_rep_id}} effective {{effective_date}}."
consumes:
- type: http
namespace: salesforce
baseUri: "https://pfizer.my.salesforce.com/services/data/v59.0"
authentication:
type: bearer
token: "$secrets.salesforce_token"
resources:
- name: territories
path: "/sobjects/Territory2/{{id}}"
inputParameters:
- name: id
in: path
operations:
- name: update-record
method: PATCH
- type: http
namespace: workday
baseUri: "https://wd5-services1.myworkday.com/ccx/service/pfizer/Staffing/v42.0"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: assignments
path: "/workers/{{employee_id}}/assignments"
inputParameters:
- name: employee_id
in: path
operations:
- name: update-assignment
method: PUT
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves healthcare provider account details from Salesforce CRM by account ID for Pfizer commercial operations.
naftiko: "0.5"
info:
label: "Salesforce HCP Account Lookup"
description: "Retrieves healthcare provider account details from Salesforce CRM by account ID for Pfizer commercial operations."
tags:
- commercial
- salesforce
- hcp
- lookup
capability:
exposes:
- type: mcp
namespace: commercial-ops
port: 8080
tools:
- name: get-hcp-account
description: "Given a Salesforce account ID, return the HCP name, specialty, prescribing tier, and territory."
inputParameters:
- name: account_id
in: body
type: string
description: "The Salesforce account ID for the healthcare provider."
call: salesforce.get-account
with:
account_id: "{{account_id}}"
outputParameters:
- name: hcp_name
type: string
mapping: "$.Name"
- name: specialty
type: string
mapping: "$.Specialty__c"
- name: tier
type: string
mapping: "$.Prescribing_Tier__c"
- name: territory
type: string
mapping: "$.Territory__c"
consumes:
- type: http
namespace: salesforce
baseUri: "https://pfizer.my.salesforce.com/services/data/v59.0"
authentication:
type: bearer
token: "$secrets.salesforce_token"
resources:
- name: accounts
path: "/sobjects/Account/{{account_id}}"
inputParameters:
- name: account_id
in: path
operations:
- name: get-account
method: GET
Syncs updated healthcare provider (HCP) account data from Salesforce to the Power BI commercial analytics dataset for territory planning and reporting.
naftiko: "0.5"
info:
label: "Salesforce Healthcare Provider Account Sync"
description: "Syncs updated healthcare provider (HCP) account data from Salesforce to the Power BI commercial analytics dataset for territory planning and reporting."
tags:
- sales
- crm
- salesforce
- power-bi
- hcp
- commercial
capability:
exposes:
- type: mcp
namespace: hcp-analytics
port: 8080
tools:
- name: sync-hcp-accounts
description: "Query Salesforce for HCP accounts updated in the last 7 days and push the updated records to the Power BI commercial analytics dataset."
inputParameters:
- name: dataset_id
in: body
type: string
description: "The Power BI dataset ID for commercial analytics."
- name: table_name
in: body
type: string
description: "The Power BI table name to push HCP data into."
steps:
- name: query-hcp-accounts
type: call
call: salesforce.query-records
with:
q: "SELECT Id,Name,Specialty__c,Territory__c,LastModifiedDate FROM Account WHERE RecordType.Name = 'HCP' AND LastModifiedDate = LAST_N_DAYS:7"
- name: push-to-powerbi
type: call
call: powerbi.push-rows
with:
dataset_id: "{{dataset_id}}"
table_name: "{{table_name}}"
rows: "{{query-hcp-accounts.records}}"
consumes:
- type: http
namespace: salesforce
baseUri: "https://pfizer.my.salesforce.com/services/data/v58.0"
authentication:
type: bearer
token: "$secrets.salesforce_token"
resources:
- name: query
path: "/query"
inputParameters:
- name: q
in: query
operations:
- name: query-records
method: GET
- type: http
namespace: powerbi
baseUri: "https://api.powerbi.com/v1.0/myorg"
authentication:
type: bearer
token: "$secrets.powerbi_token"
resources:
- name: rows
path: "/datasets/{{dataset_id}}/tables/{{table_name}}/rows"
inputParameters:
- name: dataset_id
in: path
- name: table_name
in: path
operations:
- name: push-rows
method: POST
Tracks KOL engagement activities by pulling data from Salesforce, summarizing in Snowflake, and reporting to medical affairs for Pfizer.
naftiko: "0.5"
info:
label: "Salesforce Key Opinion Leader Engagement Tracker"
description: "Tracks KOL engagement activities by pulling data from Salesforce, summarizing in Snowflake, and reporting to medical affairs for Pfizer."
tags:
- medical-affairs
- salesforce
- snowflake
- analytics
capability:
exposes:
- type: mcp
namespace: medical-affairs-analytics
port: 8080
tools:
- name: track-kol-engagement
description: "Given a therapeutic area, pull KOL engagement data, aggregate in Snowflake, and post a summary."
inputParameters:
- name: therapeutic_area
in: body
type: string
description: "The therapeutic area (e.g., oncology, immunology)."
- name: period
in: body
type: string
description: "Reporting period (e.g., Q1-2026)."
steps:
- name: pull-kol-data
type: call
call: salesforce.query
with:
q: "SELECT Name, Total_Engagements__c FROM Contact WHERE Therapeutic_Area__c = '{{therapeutic_area}}' AND KOL_Flag__c = true"
- name: aggregate-data
type: call
call: snowflake.execute-query
with:
statement: "INSERT INTO kol_engagement_summary SELECT * FROM staged_kol_data WHERE period = '{{period}}'"
warehouse: "ANALYTICS_WH"
- name: post-summary
type: call
call: msteams.send-message
with:
channel_id: "$secrets.med_affairs_channel"
text: "KOL Engagement Summary for {{therapeutic_area}} ({{period}}): {{pull-kol-data.totalSize}} KOLs tracked."
consumes:
- type: http
namespace: salesforce
baseUri: "https://pfizer.my.salesforce.com/services/data/v59.0"
authentication:
type: bearer
token: "$secrets.salesforce_token"
resources:
- name: query
path: "/query"
operations:
- name: query
method: GET
- type: http
namespace: snowflake
baseUri: "https://pfizer.snowflakecomputing.com/api/v2"
authentication:
type: bearer
token: "$secrets.snowflake_token"
resources:
- name: statements
path: "/statements"
operations:
- name: execute-query
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Manages contract renewal workflows by checking expiring contracts in SAP Ariba, creating ServiceNow tasks, and notifying procurement for Pfizer.
naftiko: "0.5"
info:
label: "SAP Ariba Contract Renewal Workflow"
description: "Manages contract renewal workflows by checking expiring contracts in SAP Ariba, creating ServiceNow tasks, and notifying procurement for Pfizer."
tags:
- procurement
- sap-ariba
- servicenow
- contract-management
capability:
exposes:
- type: mcp
namespace: procurement-contracts
port: 8080
tools:
- name: process-contract-renewal
description: "Given a contract ID, check renewal terms, create a ServiceNow task, and notify procurement."
inputParameters:
- name: contract_id
in: body
type: string
description: "The SAP Ariba contract ID."
- name: contract_owner
in: body
type: string
description: "The contract owner name."
steps:
- name: get-contract
type: call
call: ariba.get-contract
with:
contract_id: "{{contract_id}}"
- name: create-renewal-task
type: call
call: servicenow.create-incident
with:
short_description: "Contract Renewal: {{get-contract.title}} — Expires {{get-contract.end_date}}"
category: "procurement"
- name: notify-procurement
type: call
call: msteams.send-message
with:
channel_id: "$secrets.procurement_channel"
text: "Contract Renewal: {{get-contract.title}} ({{contract_id}}) expires {{get-contract.end_date}}. Task: {{create-renewal-task.number}}."
consumes:
- type: http
namespace: ariba
baseUri: "https://openapi.ariba.com/api/procurement/v2/pfizer"
authentication:
type: bearer
token: "$secrets.ariba_token"
resources:
- name: contracts
path: "/contracts/{{contract_id}}"
inputParameters:
- name: contract_id
in: path
operations:
- name: get-contract
method: GET
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves a vendor contract from SAP Ariba by contract ID and returns its status, expiry date, and total committed spend.
naftiko: "0.5"
info:
label: "SAP Ariba Vendor Contract Lookup"
description: "Retrieves a vendor contract from SAP Ariba by contract ID and returns its status, expiry date, and total committed spend."
tags:
- procurement
- sap-ariba
- contracts
- lookup
capability:
exposes:
- type: mcp
namespace: procurement-lookup
port: 8080
tools:
- name: get-vendor-contract
description: "Given an SAP Ariba contract ID, return the contract status, effective date, expiry date, and total committed spend."
inputParameters:
- name: contract_id
in: body
type: string
description: "The SAP Ariba contract ID to retrieve (e.g., 'CW123456')."
call: ariba.get-contract
with:
contract_id: "{{contract_id}}"
outputParameters:
- name: status
type: string
mapping: "$.Status"
- name: expiry_date
type: string
mapping: "$.ExpiryDate"
- name: total_spend
type: string
mapping: "$.TotalCommittedAmount"
- name: vendor_name
type: string
mapping: "$.VendorName"
consumes:
- type: http
namespace: ariba
baseUri: "https://openapi.ariba.com/api/contract-management/v1"
authentication:
type: bearer
token: "$secrets.ariba_token"
resources:
- name: contracts
path: "/contracts/{{contract_id}}"
inputParameters:
- name: contract_id
in: path
operations:
- name: get-contract
method: GET
Retrieves batch genealogy and traceability data from SAP for a given batch number in Pfizer manufacturing.
naftiko: "0.5"
info:
label: "SAP Batch Genealogy Lookup"
description: "Retrieves batch genealogy and traceability data from SAP for a given batch number in Pfizer manufacturing."
tags:
- manufacturing
- sap
- batch-tracking
- quality
capability:
exposes:
- type: mcp
namespace: manufacturing-ops
port: 8080
tools:
- name: get-batch-genealogy
description: "Given a batch number and plant code, return the batch creation date, material, and expiry date."
inputParameters:
- name: batch_number
in: body
type: string
description: "The SAP batch number."
- name: plant
in: body
type: string
description: "The SAP plant code."
call: sap.get-batch
with:
batch_number: "{{batch_number}}"
plant: "{{plant}}"
outputParameters:
- name: material
type: string
mapping: "$.d.Material"
- name: manufacture_date
type: string
mapping: "$.d.ManufactureDate"
- name: shelf_life_expiry
type: string
mapping: "$.d.ShelfLifeExpirationDate"
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_BATCH_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: batches
path: "/A_Batch(Material='',Batch='{{batch_number}}',Plant='{{plant}}')"
inputParameters:
- name: batch_number
in: path
- name: plant
in: path
operations:
- name: get-batch
method: GET
Retrieves a pending SAP Concur expense report for approval, approves it, and notifies the submitter via Microsoft Teams.
naftiko: "0.5"
info:
label: "SAP Concur Travel Expense Approval"
description: "Retrieves a pending SAP Concur expense report for approval, approves it, and notifies the submitter via Microsoft Teams."
tags:
- finance
- expense-management
- sap-concur
- approval
- microsoft-teams
capability:
exposes:
- type: mcp
namespace: expense-approval
port: 8080
tools:
- name: approve-expense-report
description: "Given a SAP Concur expense report ID and approver comment, retrieve the report details, approve it, and notify the submitter via Teams."
inputParameters:
- name: report_id
in: body
type: string
description: "The SAP Concur expense report ID to approve."
- name: approver_comment
in: body
type: string
description: "Approval comment to attach to the action."
steps:
- name: get-report
type: call
call: concur.get-report
with:
report_id: "{{report_id}}"
- name: approve-report
type: call
call: concur.approve-report
with:
report_id: "{{report_id}}"
comment: "{{approver_comment}}"
- name: notify-submitter
type: call
call: msteams.send-message
with:
channel_id: "{{get-report.submitter_email}}"
text: "Your expense report '{{get-report.name}}' (${{get-report.total}}) has been approved. SAP Concur updated."
consumes:
- type: http
namespace: concur
baseUri: "https://www.concursolutions.com/api/v3.0"
authentication:
type: bearer
token: "$secrets.concur_token"
resources:
- name: reports
path: "/expense/reports/{{report_id}}"
inputParameters:
- name: report_id
in: path
operations:
- name: get-report
method: GET
- name: approve-report
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Checks travel expense reports for policy violations, creates audit findings in ServiceNow, and notifies finance for Pfizer.
naftiko: "0.5"
info:
label: "SAP Concur Travel Policy Compliance Checker"
description: "Checks travel expense reports for policy violations, creates audit findings in ServiceNow, and notifies finance for Pfizer."
tags:
- finance
- sap-concur
- compliance
- audit
capability:
exposes:
- type: mcp
namespace: finance-compliance
port: 8080
tools:
- name: check-travel-compliance
description: "Given an expense report ID, check for policy violations, create audit findings, and notify the compliance team."
inputParameters:
- name: report_id
in: body
type: string
description: "The SAP Concur expense report ID."
- name: employee_id
in: body
type: string
description: "The employee ID who submitted the report."
steps:
- name: get-report
type: call
call: concur.get-expense-report
with:
report_id: "{{report_id}}"
- name: log-findings
type: call
call: servicenow.create-incident
with:
short_description: "Travel Compliance Review: Report {{report_id}}"
category: "finance_audit"
- name: notify-finance
type: call
call: msteams.send-message
with:
channel_id: "$secrets.finance_compliance_channel"
text: "Travel Compliance: Report {{report_id}} by Employee {{employee_id}}. Total: {{get-report.total}}. Violations: {{get-report.violations_count}}. SNOW: {{log-findings.number}}."
consumes:
- type: http
namespace: concur
baseUri: "https://us2.api.concursolutions.com/api/v3.0"
authentication:
type: bearer
token: "$secrets.concur_token"
resources:
- name: expense-reports
path: "/expense/reports/{{report_id}}"
inputParameters:
- name: report_id
in: path
operations:
- name: get-expense-report
method: GET
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Reports cost center budget variances from SAP, creates finance review tasks, and notifies the finance team for Pfizer.
naftiko: "0.5"
info:
label: "SAP Cost Center Budget Variance Reporter"
description: "Reports cost center budget variances from SAP, creates finance review tasks, and notifies the finance team for Pfizer."
tags:
- finance
- sap
- budgeting
- reporting
capability:
exposes:
- type: mcp
namespace: finance-reporting
port: 8080
tools:
- name: report-budget-variance
description: "Given a cost center and period, calculate budget variance, create a review task, and notify finance."
inputParameters:
- name: cost_center
in: body
type: string
description: "The SAP cost center."
- name: fiscal_period
in: body
type: string
description: "The fiscal period (e.g., 2026-03)."
steps:
- name: get-variance
type: call
call: sap.get-budget-variance
with:
cost_center: "{{cost_center}}"
period: "{{fiscal_period}}"
- name: create-review
type: call
call: servicenow.create-incident
with:
short_description: "Budget Variance: CC {{cost_center}} — {{fiscal_period}}"
category: "finance"
- name: notify-finance
type: call
call: msteams.send-message
with:
channel_id: "$secrets.finance_channel"
text: "Budget Variance: CC {{cost_center}} for {{fiscal_period}}. Variance: {{get-variance.variance}}. Review: {{create-review.number}}."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_COSTCENTER_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: create-record
method: POST
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves cost element master data from SAP for Pfizer finance and controlling operations.
naftiko: "0.5"
info:
label: "SAP Cost Element Lookup"
description: "Retrieves cost element master data from SAP for Pfizer finance and controlling operations."
tags:
- finance
- sap
- controlling
- lookup
capability:
exposes:
- type: mcp
namespace: finance-controlling
port: 8080
tools:
- name: get-cost-element
description: "Given a cost element code, return the description, category, and controlling area."
inputParameters:
- name: cost_element
in: body
type: string
description: "The SAP cost element code."
call: sap.get-cost-element
with:
cost_element: "{{cost_element}}"
outputParameters:
- name: description
type: string
mapping: "$.d.CostElementDescription"
- name: category
type: string
mapping: "$.d.CostElementCategory"
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_COSTELEMENT_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: get-record
method: GET
Retrieves outbound delivery document details from SAP by delivery number for Pfizer logistics operations.
naftiko: "0.5"
info:
label: "SAP Delivery Document Lookup"
description: "Retrieves outbound delivery document details from SAP by delivery number for Pfizer logistics operations."
tags:
- logistics
- sap
- delivery
- lookup
capability:
exposes:
- type: mcp
namespace: logistics-ops
port: 8080
tools:
- name: get-delivery-document
description: "Given a SAP delivery number, return the ship-to party, delivery date, and total weight."
inputParameters:
- name: delivery_number
in: body
type: string
description: "The SAP delivery document number."
call: sap.get-delivery
with:
delivery_number: "{{delivery_number}}"
outputParameters:
- name: ship_to
type: string
mapping: "$.d.ShipToParty"
- name: delivery_date
type: string
mapping: "$.d.DeliveryDate"
- name: total_weight
type: string
mapping: "$.d.HeaderGrossWeight"
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_OUTBOUND_DELIVERY_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: get-record
method: GET
Creates breakdown maintenance notifications in SAP when equipment failures are reported and notifies the maintenance team for Pfizer.
naftiko: "0.5"
info:
label: "SAP Equipment Breakdown Incident Creator"
description: "Creates breakdown maintenance notifications in SAP when equipment failures are reported and notifies the maintenance team for Pfizer."
tags:
- manufacturing
- sap
- maintenance
- incident
capability:
exposes:
- type: mcp
namespace: manufacturing-breakdown
port: 8080
tools:
- name: create-breakdown-incident
description: "Given equipment failure details, create a SAP breakdown notification and a ServiceNow incident."
inputParameters:
- name: equipment_id
in: body
type: string
description: "The SAP equipment ID."
- name: failure_description
in: body
type: string
description: "Description of the equipment failure."
- name: plant
in: body
type: string
description: "The manufacturing plant code."
- name: priority
in: body
type: string
description: "Incident priority (P1-P4)."
steps:
- name: create-sap-notification
type: call
call: sap.create-maintenance-notification
with:
equipment: "{{equipment_id}}"
notification_type: "M2"
description: "{{failure_description}}"
plant: "{{plant}}"
- name: create-snow-incident
type: call
call: servicenow.create-incident
with:
short_description: "Equipment Breakdown: {{equipment_id}} at Plant {{plant}}"
priority: "{{priority}}"
description: "Equipment: {{equipment_id}} | Failure: {{failure_description}} | Plant: {{plant}} | SAP: {{create-sap-notification.notification_number}}"
- name: notify-maintenance
type: call
call: msteams.send-message
with:
channel_id: "$secrets.maintenance_channel"
text: "EQUIPMENT BREAKDOWN: {{equipment_id}} at Plant {{plant}}. Priority: {{priority}}. SAP: {{create-sap-notification.notification_number}}. SNOW: {{create-snow-incident.number}}."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_MAINTNOTIFICATION_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: get-record
method: GET
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Manages the release of finished goods by updating SAP batch status, recording quality release in ServiceNow, and notifying distribution for Pfizer.
naftiko: "0.5"
info:
label: "SAP Finished Goods Release Workflow"
description: "Manages the release of finished goods by updating SAP batch status, recording quality release in ServiceNow, and notifying distribution for Pfizer."
tags:
- manufacturing
- sap
- quality
- distribution
capability:
exposes:
- type: mcp
namespace: manufacturing-release
port: 8080
tools:
- name: release-finished-goods
description: "Given batch and quality details, update SAP batch status to released, log in ServiceNow, and notify distribution."
inputParameters:
- name: batch_number
in: body
type: string
description: "The SAP batch number."
- name: material_number
in: body
type: string
description: "The material number."
- name: plant
in: body
type: string
description: "The manufacturing plant code."
- name: quality_decision
in: body
type: string
description: "Quality decision (release, reject, conditional)."
steps:
- name: update-batch
type: call
call: sap.update-batch-status
with:
batch_number: "{{batch_number}}"
material: "{{material_number}}"
plant: "{{plant}}"
status: "{{quality_decision}}"
- name: log-release
type: call
call: servicenow.create-incident
with:
short_description: "FG Release: Batch {{batch_number}} — {{quality_decision}}"
category: "manufacturing_quality"
description: "Batch: {{batch_number}} | Material: {{material_number}} | Plant: {{plant}} | Decision: {{quality_decision}}"
- name: notify-distribution
type: call
call: msteams.send-message
with:
channel_id: "$secrets.distribution_channel"
text: "Finished Goods Release: Batch {{batch_number}} ({{material_number}}) at Plant {{plant}}. Decision: {{quality_decision}}. SNOW: {{log-release.number}}."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_BATCH_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: get-record
method: GET
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Processes goods receipt in SAP, triggers quality inspection, and notifies the warehouse team upon completion for Pfizer.
naftiko: "0.5"
info:
label: "SAP Goods Receipt and Quality Release"
description: "Processes goods receipt in SAP, triggers quality inspection, and notifies the warehouse team upon completion for Pfizer."
tags:
- supply-chain
- sap
- quality
- warehouse
capability:
exposes:
- type: mcp
namespace: warehouse-ops
port: 8080
tools:
- name: process-goods-receipt
description: "Given a purchase order and delivery details, post goods receipt, trigger quality inspection, and notify warehouse."
inputParameters:
- name: po_number
in: body
type: string
description: "The SAP purchase order number."
- name: delivery_number
in: body
type: string
description: "The inbound delivery number."
- name: plant
in: body
type: string
description: "The receiving plant code."
steps:
- name: post-goods-receipt
type: call
call: sap.post-goods-receipt
with:
po_number: "{{po_number}}"
delivery: "{{delivery_number}}"
plant: "{{plant}}"
- name: trigger-qi
type: call
call: sap.create-inspection-lot
with:
material_document: "{{post-goods-receipt.material_document}}"
plant: "{{plant}}"
- name: notify-warehouse
type: call
call: msteams.send-message
with:
channel_id: "$secrets.warehouse_channel"
text: "Goods Receipt for PO {{po_number}}, Delivery {{delivery_number}} at Plant {{plant}}. Material Doc: {{post-goods-receipt.material_document}}. QI Lot: {{trigger-qi.inspection_lot}}."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_MATERIAL_DOCUMENT_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: create-record
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Reconciles intercompany billing documents in SAP across company codes and creates exception reports for Pfizer finance operations.
naftiko: "0.5"
info:
label: "SAP Intercompany Billing Reconciliation"
description: "Reconciles intercompany billing documents in SAP across company codes and creates exception reports for Pfizer finance operations."
tags:
- finance
- sap
- billing
- reconciliation
capability:
exposes:
- type: mcp
namespace: finance-intercompany
port: 8080
tools:
- name: reconcile-intercompany-billing
description: "Given company codes and a billing period, reconcile intercompany transactions and report exceptions."
inputParameters:
- name: sender_company
in: body
type: string
description: "The sending company code."
- name: receiver_company
in: body
type: string
description: "The receiving company code."
- name: billing_period
in: body
type: string
description: "The billing period to reconcile."
steps:
- name: get-sender-docs
type: call
call: sap.get-billing-documents
with:
company_code: "{{sender_company}}"
period: "{{billing_period}}"
- name: get-receiver-docs
type: call
call: sap.get-billing-documents
with:
company_code: "{{receiver_company}}"
period: "{{billing_period}}"
- name: create-exception-report
type: call
call: servicenow.create-incident
with:
short_description: "IC Billing Reconciliation: {{sender_company}} to {{receiver_company}} — {{billing_period}}"
category: "finance_reconciliation"
- name: notify-finance
type: call
call: msteams.send-message
with:
channel_id: "$secrets.finance_ic_channel"
text: "IC Billing Reconciliation: {{sender_company}} to {{receiver_company}} for {{billing_period}}. Sender docs: {{get-sender-docs.count}}. Receiver docs: {{get-receiver-docs.count}}. SNOW: {{create-exception-report.number}}."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_BILLING_DOCUMENT_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: get-record
method: GET
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves current inventory stock levels from SAP for a material at a given plant for Pfizer supply chain operations.
naftiko: "0.5"
info:
label: "SAP Inventory Stock Lookup"
description: "Retrieves current inventory stock levels from SAP for a material at a given plant for Pfizer supply chain operations."
tags:
- supply-chain
- sap
- inventory
- manufacturing
capability:
exposes:
- type: mcp
namespace: supply-chain-ops
port: 8080
tools:
- name: get-stock-level
description: "Given a material number and plant code, return the unrestricted stock, quality inspection stock, and blocked stock quantities."
inputParameters:
- name: material_number
in: body
type: string
description: "The SAP material number."
- name: plant
in: body
type: string
description: "The SAP plant code."
call: sap.get-stock
with:
material_number: "{{material_number}}"
plant: "{{plant}}"
outputParameters:
- name: unrestricted
type: string
mapping: "$.d.MatlWrhsStkQtyInMatlBaseUnit"
- name: quality_inspection
type: string
mapping: "$.d.QualityInspectionStockQty"
- name: blocked
type: string
mapping: "$.d.BlockedStockQty"
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_MATERIAL_STOCK_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: stock
path: "/A_MatlStkInAcctMod(Material='{{material_number}}',Plant='{{plant}}')"
inputParameters:
- name: material_number
in: path
- name: plant
in: path
operations:
- name: get-stock
method: GET
Checks SAP financial period-end close progress for the accounts payable ledger and posts a completion status to the finance team's Microsoft Teams channel.
naftiko: "0.5"
info:
label: "SAP Invoice Period-End Close Status"
description: "Checks SAP financial period-end close progress for the accounts payable ledger and posts a completion status to the finance team's Microsoft Teams channel."
tags:
- finance
- sap
- period-close
- reporting
- microsoft-teams
capability:
exposes:
- type: mcp
namespace: finance-close
port: 8080
tools:
- name: monitor-ap-period-close
description: "Given a fiscal period and company code, check the SAP AP period-end close status and post a summary to the finance Teams channel."
inputParameters:
- name: fiscal_period
in: body
type: string
description: "The SAP fiscal period to check (e.g., '006/2026')."
- name: company_code
in: body
type: string
description: "The SAP company code for Pfizer (e.g., 'US01')."
- name: teams_channel_id
in: body
type: string
description: "Teams channel ID for the finance close status."
steps:
- name: get-close-status
type: call
call: sap.get-close-status
with:
fiscal_period: "{{fiscal_period}}"
company_code: "{{company_code}}"
- name: post-status
type: call
call: msteams.send-message
with:
channel_id: "{{teams_channel_id}}"
text: "AP Period Close Status {{fiscal_period}} ({{company_code}}): {{get-close-status.completion_pct}}% complete. Open items: {{get-close-status.open_count}}."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/FCO_PI_CLOSE_COCKPIT_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: close-status
path: "/ClosingTaskSet"
inputParameters:
- name: fiscal_period
in: query
- name: company_code
in: query
operations:
- name: get-close-status
method: GET
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Validates invoices by performing three-way matching in SAP, logs exceptions in ServiceNow, and notifies accounts payable for Pfizer.
naftiko: "0.5"
info:
label: "SAP Invoice Three-Way Match Validator"
description: "Validates invoices by performing three-way matching in SAP, logs exceptions in ServiceNow, and notifies accounts payable for Pfizer."
tags:
- finance
- sap
- accounts-payable
- compliance
capability:
exposes:
- type: mcp
namespace: finance-ap
port: 8080
tools:
- name: validate-invoice-match
description: "Given an invoice number, perform three-way match validation, log exceptions, and notify AP."
inputParameters:
- name: invoice_number
in: body
type: string
description: "The SAP invoice document number."
- name: company_code
in: body
type: string
description: "The SAP company code."
steps:
- name: check-match
type: call
call: sap.validate-three-way-match
with:
invoice_number: "{{invoice_number}}"
company_code: "{{company_code}}"
- name: log-exception
type: call
call: servicenow.create-incident
with:
short_description: "Invoice Match Exception: {{invoice_number}}"
category: "accounts_payable"
- name: notify-ap
type: call
call: msteams.send-message
with:
channel_id: "$secrets.ap_channel"
text: "Invoice Match: {{invoice_number}} in Company {{company_code}}. Status: {{check-match.status}}. Variance: {{check-match.variance}}. SNOW: {{log-exception.number}}."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_SUPPLIERINVOICE_PROCESS_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: create-record
method: POST
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves material master data from SAP S/4HANA by material number for Pfizer manufacturing and supply chain operations.
naftiko: "0.5"
info:
label: "SAP Material Master Lookup"
description: "Retrieves material master data from SAP S/4HANA by material number for Pfizer manufacturing and supply chain operations."
tags:
- manufacturing
- sap
- supply-chain
- lookup
capability:
exposes:
- type: mcp
namespace: supply-chain
port: 8080
tools:
- name: get-material
description: "Given a SAP material number, return the material description, base unit of measure, and material group."
inputParameters:
- name: material_number
in: body
type: string
description: "The SAP material number (e.g., MAT-001234)."
call: sap.get-material
with:
material_number: "{{material_number}}"
outputParameters:
- name: description
type: string
mapping: "$.d.MaterialDescription"
- name: base_uom
type: string
mapping: "$.d.BaseUnit"
- name: material_group
type: string
mapping: "$.d.MaterialGroup"
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_PRODUCT_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: materials
path: "/A_Product('{{material_number}}')"
inputParameters:
- name: material_number
in: path
operations:
- name: get-material
method: GET
Handles MRP run exceptions from SAP by creating supply chain alerts, logging in ServiceNow, and notifying the planning team for Pfizer.
naftiko: "0.5"
info:
label: "SAP MRP Run Exception Handler"
description: "Handles MRP run exceptions from SAP by creating supply chain alerts, logging in ServiceNow, and notifying the planning team for Pfizer."
tags:
- supply-chain
- sap
- planning
- manufacturing
capability:
exposes:
- type: mcp
namespace: supply-planning
port: 8080
tools:
- name: handle-mrp-exception
description: "Given MRP exception details, create a ServiceNow alert and notify the supply planning team."
inputParameters:
- name: material_number
in: body
type: string
description: "The material with the MRP exception."
- name: exception_type
in: body
type: string
description: "Type of MRP exception (shortage, excess, rescheduling)."
- name: plant
in: body
type: string
description: "The plant code."
- name: quantity
in: body
type: string
description: "The exception quantity."
steps:
- name: create-alert
type: call
call: servicenow.create-incident
with:
short_description: "MRP Exception: {{exception_type}} — Material {{material_number}}"
category: "supply_planning"
- name: notify-planning
type: call
call: msteams.send-message
with:
channel_id: "$secrets.planning_channel"
text: "MRP Exception: {{exception_type}} for Material {{material_number}} at Plant {{plant}}. Qty: {{quantity}}. SNOW: {{create-alert.number}}."
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Creates planned maintenance orders in SAP for manufacturing equipment, schedules in ServiceNow, and notifies the maintenance team for Pfizer.
naftiko: "0.5"
info:
label: "SAP Planned Maintenance Order Creator"
description: "Creates planned maintenance orders in SAP for manufacturing equipment, schedules in ServiceNow, and notifies the maintenance team for Pfizer."
tags:
- manufacturing
- sap
- maintenance
- servicenow
capability:
exposes:
- type: mcp
namespace: manufacturing-maintenance
port: 8080
tools:
- name: create-maintenance-order
description: "Given equipment details, create a SAP maintenance order, a ServiceNow work order, and notify maintenance."
inputParameters:
- name: equipment_id
in: body
type: string
description: "The SAP equipment ID."
- name: maintenance_type
in: body
type: string
description: "Type of maintenance (preventive, calibration, qualification)."
- name: plant
in: body
type: string
description: "The plant code."
- name: scheduled_date
in: body
type: string
description: "Scheduled maintenance date."
steps:
- name: create-sap-order
type: call
call: sap.create-maintenance-order
with:
equipment: "{{equipment_id}}"
order_type: "{{maintenance_type}}"
plant: "{{plant}}"
- name: create-snow-work-order
type: call
call: servicenow.create-incident
with:
short_description: "Maintenance: {{maintenance_type}} — Equipment {{equipment_id}}"
category: "manufacturing_maintenance"
- name: notify-maintenance
type: call
call: msteams.send-message
with:
channel_id: "$secrets.maintenance_channel"
text: "Maintenance Scheduled: {{maintenance_type}} for Equipment {{equipment_id}} at Plant {{plant}} on {{scheduled_date}}. SAP: {{create-sap-order.order_number}}. SNOW: {{create-snow-work-order.number}}."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_MAINTENANCEORDER_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: create-record
method: POST
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves production order status and details from SAP for Pfizer manufacturing operations.
naftiko: "0.5"
info:
label: "SAP Production Order Status Lookup"
description: "Retrieves production order status and details from SAP for Pfizer manufacturing operations."
tags:
- manufacturing
- sap
- production
- lookup
capability:
exposes:
- type: mcp
namespace: manufacturing-mgmt
port: 8080
tools:
- name: get-production-order
description: "Given a SAP production order number, return the order type, status, planned quantity, and material."
inputParameters:
- name: order_number
in: body
type: string
description: "The SAP production order number."
call: sap.get-prod-order
with:
order_number: "{{order_number}}"
outputParameters:
- name: order_type
type: string
mapping: "$.d.ManufacturingOrderType"
- name: status
type: string
mapping: "$.d.MfgOrderPlannedTotalQty"
- name: material
type: string
mapping: "$.d.Material"
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_PRODUCTION_ORDER_2_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: production-orders
path: "/A_ProductionOrder_2('{{order_number}}')"
inputParameters:
- name: order_number
in: path
operations:
- name: get-prod-order
method: GET
Retrieves a SAP S/4HANA purchase order by number and returns the header status, supplier, and total amount for procurement tracking.
naftiko: "0.5"
info:
label: "SAP Purchase Order Status Lookup"
description: "Retrieves a SAP S/4HANA purchase order by number and returns the header status, supplier, and total amount for procurement tracking."
tags:
- finance
- procurement
- sap
- lookup
capability:
exposes:
- type: mcp
namespace: erp-lookup
port: 8080
tools:
- name: get-purchase-order
description: "Given a SAP purchase order number, return the PO status, supplier name, total amount, and currency."
inputParameters:
- name: po_number
in: body
type: string
description: "The SAP purchase order number (e.g., '4500098765')."
call: sap.get-po
with:
po_number: "{{po_number}}"
outputParameters:
- name: status
type: string
mapping: "$.d.OverallStatus"
- name: supplier
type: string
mapping: "$.d.Supplier.CompanyName"
- name: total_amount
type: string
mapping: "$.d.TotalAmount"
- name: currency
type: string
mapping: "$.d.TransactionCurrency"
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/MM_PUR_PO_MAINT_V2_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: purchase-orders
path: "/A_PurchaseOrder('{{po_number}}')"
inputParameters:
- name: po_number
in: path
operations:
- name: get-po
method: GET
Retrieves quality inspection lot details from SAP for Pfizer quality assurance operations.
naftiko: "0.5"
info:
label: "SAP Quality Inspection Lot Lookup"
description: "Retrieves quality inspection lot details from SAP for Pfizer quality assurance operations."
tags:
- quality
- sap
- manufacturing
- inspection
capability:
exposes:
- type: mcp
namespace: quality-mgmt
port: 8080
tools:
- name: get-inspection-lot
description: "Given an inspection lot number, return the material, inspection type, lot status, and result."
inputParameters:
- name: inspection_lot
in: body
type: string
description: "The SAP quality inspection lot number."
call: sap.get-inspection-lot
with:
inspection_lot: "{{inspection_lot}}"
outputParameters:
- name: material
type: string
mapping: "$.d.Material"
- name: inspection_type
type: string
mapping: "$.d.InspectionLotType"
- name: lot_status
type: string
mapping: "$.d.InspectionLotStatusID"
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_INSPECTIONLOT_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: inspection-lots
path: "/A_InspectionLot('{{inspection_lot}}')"
inputParameters:
- name: inspection_lot
in: path
operations:
- name: get-inspection-lot
method: GET
Tracks outbound shipments in SAP TM, updates delivery status in Salesforce, and notifies the distribution team for Pfizer.
naftiko: "0.5"
info:
label: "SAP Transport Management Shipment Tracker"
description: "Tracks outbound shipments in SAP TM, updates delivery status in Salesforce, and notifies the distribution team for Pfizer."
tags:
- supply-chain
- sap
- salesforce
- logistics
capability:
exposes:
- type: mcp
namespace: distribution-ops
port: 8080
tools:
- name: track-shipment
description: "Given a shipment ID, retrieve tracking data from SAP TM, update Salesforce, and notify distribution."
inputParameters:
- name: shipment_id
in: body
type: string
description: "The SAP Transportation Management shipment ID."
- name: salesforce_order_id
in: body
type: string
description: "The related Salesforce order ID."
steps:
- name: get-tracking
type: call
call: sap.get-shipment-status
with:
shipment_id: "{{shipment_id}}"
- name: update-salesforce
type: call
call: salesforce.update-record
with:
object_type: "Order"
id: "{{salesforce_order_id}}"
Shipping_Status__c: "{{get-tracking.status}}"
- name: notify-distribution
type: call
call: msteams.send-message
with:
channel_id: "$secrets.distribution_channel"
text: "Shipment Update: {{shipment_id}} — Status: {{get-tracking.status}}. ETA: {{get-tracking.eta}}. Salesforce updated."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_FREIGHT_ORDER_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: create-record
method: POST
- type: http
namespace: salesforce
baseUri: "https://pfizer.my.salesforce.com/services/data/v59.0"
authentication:
type: bearer
token: "$secrets.salesforce_token"
resources:
- name: orders
path: "/sobjects/Order/{{id}}"
inputParameters:
- name: id
in: path
operations:
- name: update-record
method: PATCH
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves vendor master data from SAP S/4HANA by vendor number for Pfizer procurement operations.
naftiko: "0.5"
info:
label: "SAP Vendor Master Lookup"
description: "Retrieves vendor master data from SAP S/4HANA by vendor number for Pfizer procurement operations."
tags:
- procurement
- sap
- vendor-management
- lookup
capability:
exposes:
- type: mcp
namespace: procurement-ops
port: 8080
tools:
- name: get-vendor
description: "Given a SAP vendor number, return the vendor name, payment terms, and purchasing organization."
inputParameters:
- name: vendor_number
in: body
type: string
description: "The SAP vendor account number."
call: sap.get-vendor
with:
vendor_number: "{{vendor_number}}"
outputParameters:
- name: vendor_name
type: string
mapping: "$.d.SupplierName"
- name: payment_terms
type: string
mapping: "$.d.PaymentTerms"
- name: purchasing_org
type: string
mapping: "$.d.PurchasingOrganization"
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_BUSINESS_PARTNER"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: suppliers
path: "/A_Supplier('{{vendor_number}}')"
inputParameters:
- name: vendor_number
in: path
operations:
- name: get-vendor
method: GET
Monitors warehouse capacity levels in SAP, creates planning alerts in ServiceNow, and notifies logistics when thresholds are breached for Pfizer.
naftiko: "0.5"
info:
label: "SAP Warehouse Capacity Planning Alert"
description: "Monitors warehouse capacity levels in SAP, creates planning alerts in ServiceNow, and notifies logistics when thresholds are breached for Pfizer."
tags:
- supply-chain
- sap
- warehouse
- capacity-planning
capability:
exposes:
- type: mcp
namespace: logistics-planning
port: 8080
tools:
- name: alert-warehouse-capacity
description: "Given a warehouse and capacity threshold, check current utilization and alert if exceeded."
inputParameters:
- name: warehouse_id
in: body
type: string
description: "The SAP warehouse number."
- name: threshold_percent
in: body
type: integer
description: "Capacity utilization threshold percentage."
- name: plant
in: body
type: string
description: "The SAP plant code."
steps:
- name: check-capacity
type: call
call: sap.get-warehouse-utilization
with:
warehouse: "{{warehouse_id}}"
plant: "{{plant}}"
- name: create-alert
type: call
call: servicenow.create-incident
with:
short_description: "Warehouse Capacity Alert: {{warehouse_id}} at {{check-capacity.utilization}}%"
category: "logistics"
- name: notify-logistics
type: call
call: msteams.send-message
with:
channel_id: "$secrets.logistics_channel"
text: "Warehouse Capacity: {{warehouse_id}} at Plant {{plant}} is at {{check-capacity.utilization}}% (threshold: {{threshold_percent}}%). SNOW: {{create-alert.number}}."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_WAREHOUSE_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: create-record
method: POST
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves configuration item details from ServiceNow CMDB by asset tag for Pfizer IT asset management.
naftiko: "0.5"
info:
label: "ServiceNow CMDB Asset Lookup"
description: "Retrieves configuration item details from ServiceNow CMDB by asset tag for Pfizer IT asset management."
tags:
- it-operations
- servicenow
- cmdb
- lookup
capability:
exposes:
- type: mcp
namespace: it-ops
port: 8080
tools:
- name: get-cmdb-asset
description: "Given an asset tag, return the CI name, class, operational status, and assigned support group."
inputParameters:
- name: asset_tag
in: body
type: string
description: "The ServiceNow asset tag identifier."
call: servicenow.get-ci
with:
asset_tag: "{{asset_tag}}"
outputParameters:
- name: ci_name
type: string
mapping: "$.result.name"
- name: ci_class
type: string
mapping: "$.result.sys_class_name"
- name: operational_status
type: string
mapping: "$.result.operational_status"
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.service-now.com/api/now"
authentication:
type: basic
username: "$secrets.servicenow_user"
password: "$secrets.servicenow_password"
resources:
- name: cmdb-ci
path: "/table/cmdb_ci?sysparm_query=asset_tag={{asset_tag}}"
inputParameters:
- name: asset_tag
in: query
operations:
- name: get-ci
method: GET
Creates a GxP-compliant change control request in ServiceNow for validated systems and notifies the quality assurance team in Microsoft Teams for review.
naftiko: "0.5"
info:
label: "ServiceNow GxP Change Control Request"
description: "Creates a GxP-compliant change control request in ServiceNow for validated systems and notifies the quality assurance team in Microsoft Teams for review."
tags:
- compliance
- quality
- servicenow
- microsoft-teams
- change-management
- gxp
capability:
exposes:
- type: mcp
namespace: quality-ops
port: 8080
tools:
- name: submit-gxp-change-control
description: "Given a system name, change description, GxP impact assessment, and QA channel, create a ServiceNow GxP change control request and notify QA for review."
inputParameters:
- name: system_name
in: body
type: string
description: "The GxP validated system being changed (e.g., 'LIMS', 'ERP-Production')."
- name: change_description
in: body
type: string
description: "Full description of the change and its scope."
- name: gxp_impact
in: body
type: string
description: "GxP impact assessment: 'Direct', 'Indirect', or 'No Impact'."
- name: qa_channel_id
in: body
type: string
description: "Teams channel ID for the QA review notification."
steps:
- name: create-change-control
type: call
call: servicenow.create-change
with:
short_description: "GxP Change Control: {{system_name}} — {{change_description}}"
category: "gxp_change_control"
description: "System: {{system_name}} | GxP Impact: {{gxp_impact}} | Change: {{change_description}}"
- name: notify-qa
type: call
call: msteams.send-message
with:
channel_id: "{{qa_channel_id}}"
text: "GxP Change Control Submitted: {{system_name}} | Impact: {{gxp_impact}} | CHG: {{create-change-control.number}} | Please review and approve in ServiceNow."
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.service-now.com/api/now"
authentication:
type: basic
username: "$secrets.servicenow_user"
password: "$secrets.servicenow_password"
resources:
- name: changes
path: "/table/change_request"
operations:
- name: create-change
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves a ServiceNow incident by ticket number and returns its current state, priority, assignment group, and resolution details.
naftiko: "0.5"
info:
label: "ServiceNow Incident Lookup"
description: "Retrieves a ServiceNow incident by ticket number and returns its current state, priority, assignment group, and resolution details."
tags:
- itsm
- servicenow
- lookup
capability:
exposes:
- type: mcp
namespace: itsm-lookup
port: 8080
tools:
- name: get-incident
description: "Given a ServiceNow incident number, return the incident's state, priority, assigned group, short description, and resolution code."
inputParameters:
- name: incident_number
in: body
type: string
description: "The ServiceNow incident number (e.g., 'INC0054321')."
call: servicenow.get-incident
with:
number: "{{incident_number}}"
outputParameters:
- name: state
type: string
mapping: "$.result.state"
- name: priority
type: string
mapping: "$.result.priority"
- name: assigned_to
type: string
mapping: "$.result.assigned_to.display_value"
- name: short_description
type: string
mapping: "$.result.short_description"
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.service-now.com/api/now"
authentication:
type: basic
username: "$secrets.servicenow_user"
password: "$secrets.servicenow_password"
resources:
- name: incidents
path: "/table/incident"
inputParameters:
- name: number
in: query
operations:
- name: get-incident
method: GET
Retrieves standard operating procedure document metadata from SharePoint by document name for Pfizer quality operations.
naftiko: "0.5"
info:
label: "SharePoint SOP Document Retrieval"
description: "Retrieves standard operating procedure document metadata from SharePoint by document name for Pfizer quality operations."
tags:
- quality
- sharepoint
- document-management
- sop
capability:
exposes:
- type: mcp
namespace: quality-ops
port: 8080
tools:
- name: get-sop-document
description: "Given an SOP document name or ID, return the document title, version, approval status, and URL."
inputParameters:
- name: document_name
in: body
type: string
description: "The SOP document name or ID."
call: sharepoint.get-document
with:
document_name: "{{document_name}}"
outputParameters:
- name: title
type: string
mapping: "$.d.Title"
- name: version
type: string
mapping: "$.d.UIVersionLabel"
- name: modified
type: string
mapping: "$.d.Modified"
consumes:
- type: http
namespace: sharepoint
baseUri: "https://pfizer.sharepoint.com/_api/web"
authentication:
type: bearer
token: "$secrets.sharepoint_token"
resources:
- name: files
path: "/GetFileByServerRelativeUrl('/sites/SOPs/{{document_name}}')"
inputParameters:
- name: document_name
in: path
operations:
- name: get-document
method: GET
Validates training records in SharePoint against Workday assignments and creates compliance tickets for gaps for Pfizer.
naftiko: "0.5"
info:
label: "SharePoint Training Record Validator"
description: "Validates training records in SharePoint against Workday assignments and creates compliance tickets for gaps for Pfizer."
tags:
- quality
- sharepoint
- workday
- compliance
capability:
exposes:
- type: mcp
namespace: quality-training
port: 8080
tools:
- name: validate-training-records
description: "Given a department and training program, cross-reference SharePoint records with Workday and report gaps."
inputParameters:
- name: department
in: body
type: string
description: "The department to validate."
- name: training_program
in: body
type: string
description: "The training program name."
steps:
- name: get-sharepoint-records
type: call
call: sharepoint.get-training-records
with:
department: "{{department}}"
program: "{{training_program}}"
- name: get-workday-assignments
type: call
call: workday.get-training-assignments
with:
department: "{{department}}"
program: "{{training_program}}"
- name: create-gap-ticket
type: call
call: servicenow.create-incident
with:
short_description: "Training Compliance Gap: {{department}} — {{training_program}}"
category: "quality_compliance"
- name: notify-quality
type: call
call: msteams.send-message
with:
channel_id: "$secrets.quality_training_channel"
text: "Training Gap Alert: {{department}} for {{training_program}}. SharePoint: {{get-sharepoint-records.count}}. Workday: {{get-workday-assignments.count}}. SNOW: {{create-gap-ticket.number}}."
consumes:
- type: http
namespace: sharepoint
baseUri: "https://pfizer.sharepoint.com/_api/web"
authentication:
type: bearer
token: "$secrets.sharepoint_token"
resources:
- name: lists
path: "/lists"
operations:
- name: get-training-records
method: GET
- type: http
namespace: workday
baseUri: "https://wd5-services1.myworkday.com/ccx/service/pfizer/Learning/v42.0"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: training
path: "/learningAssignments"
operations:
- name: get-training-assignments
method: GET
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Monitors Snowflake task execution history for clinical data pipelines and alerts the data engineering team via Teams if failures are detected.
naftiko: "0.5"
info:
label: "Snowflake Clinical Data Pipeline Monitor"
description: "Monitors Snowflake task execution history for clinical data pipelines and alerts the data engineering team via Teams if failures are detected."
tags:
- data
- analytics
- snowflake
- clinical-trials
- monitoring
- microsoft-teams
capability:
exposes:
- type: mcp
namespace: clinical-data-ops
port: 8080
tools:
- name: monitor-clinical-pipelines
description: "Given a Snowflake database and schema for clinical data pipelines, query for task failures in the past 24 hours and post an alert to the data engineering Teams channel."
inputParameters:
- name: database
in: body
type: string
description: "The Snowflake database name for clinical data (e.g., 'CLINICAL_DB')."
- name: schema
in: body
type: string
description: "The Snowflake schema containing clinical data pipeline tasks."
- name: teams_channel_id
in: body
type: string
description: "Teams channel ID for data engineering alerts."
steps:
- name: check-task-failures
type: call
call: snowflake.query-task-history
with:
database: "{{database}}"
schema: "{{schema}}"
- name: post-alert
type: call
call: msteams.send-message
with:
channel_id: "{{teams_channel_id}}"
text: "Clinical Pipeline Health ({{database}}.{{schema}}): {{check-task-failures.failed_count}} failures in 24h. Failed tasks: {{check-task-failures.failed_task_names}}."
consumes:
- type: http
namespace: snowflake
baseUri: "https://pfizer.snowflakecomputing.com/api/v2"
authentication:
type: bearer
token: "$secrets.snowflake_token"
resources:
- name: task-history
path: "/databases/{{database}}/schemas/{{schema}}/tasks"
inputParameters:
- name: database
in: path
- name: schema
in: path
operations:
- name: query-task-history
method: GET
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Executes a predefined SQL query against the Pfizer clinical data warehouse in Snowflake and returns summary results.
naftiko: "0.5"
info:
label: "Snowflake Clinical Query Runner"
description: "Executes a predefined SQL query against the Pfizer clinical data warehouse in Snowflake and returns summary results."
tags:
- clinical-trials
- snowflake
- data-warehouse
- analytics
capability:
exposes:
- type: mcp
namespace: clinical-analytics
port: 8080
tools:
- name: run-clinical-query
description: "Given a query identifier and optional study ID filter, execute the corresponding Snowflake query and return results."
inputParameters:
- name: query_id
in: body
type: string
description: "Predefined query identifier (e.g., enrollment-summary, ae-counts)."
- name: study_id
in: body
type: string
description: "Optional clinical study ID filter."
call: snowflake.execute-query
with:
query_id: "{{query_id}}"
study_id: "{{study_id}}"
outputParameters:
- name: row_count
type: integer
mapping: "$.resultSetMetaData.numRows"
- name: data
type: array
mapping: "$.data"
consumes:
- type: http
namespace: snowflake
baseUri: "https://pfizer.snowflakecomputing.com/api/v2"
authentication:
type: bearer
token: "$secrets.snowflake_token"
resources:
- name: statements
path: "/statements"
operations:
- name: execute-query
method: POST
Detects shipment delays in SAP, creates a ServiceNow case, and alerts the logistics team for Pfizer.
naftiko: "0.5"
info:
label: "Supply Chain Shipment Delay Escalation"
description: "Detects shipment delays in SAP, creates a ServiceNow case, and alerts the logistics team for Pfizer."
tags:
- supply-chain
- sap
- servicenow
- logistics
capability:
exposes:
- type: mcp
namespace: supply-chain-ops
port: 8080
tools:
- name: escalate-shipment-delay
description: "Given a delivery number and delay reason, create a ServiceNow case and notify supply chain leadership."
inputParameters:
- name: delivery_number
in: body
type: string
description: "The SAP delivery number."
- name: delay_reason
in: body
type: string
description: "Reason for the shipment delay."
- name: expected_date
in: body
type: string
description: "Originally expected delivery date."
- name: new_date
in: body
type: string
description: "Revised delivery date."
steps:
- name: create-sc-case
type: call
call: servicenow.create-incident
with:
short_description: "Shipment Delay: Delivery {{delivery_number}}"
category: "supply_chain"
description: "Delivery: {{delivery_number}} | Reason: {{delay_reason}} | Original: {{expected_date}} | Revised: {{new_date}}"
- name: notify-logistics
type: call
call: msteams.send-message
with:
channel_id: "$secrets.supply_chain_channel"
text: "Supply Chain Alert: Delivery {{delivery_number}} delayed from {{expected_date}} to {{new_date}}. Reason: {{delay_reason}}. Case: {{create-sc-case.number}}."
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Checks the last extract refresh status for a Tableau workbook for Pfizer analytics operations.
naftiko: "0.5"
info:
label: "Tableau Workbook Refresh Status"
description: "Checks the last extract refresh status for a Tableau workbook for Pfizer analytics operations."
tags:
- analytics
- tableau
- reporting
- lookup
capability:
exposes:
- type: mcp
namespace: analytics-tableau
port: 8080
tools:
- name: get-workbook-refresh
description: "Given a Tableau workbook ID, return the last refresh status and extract time."
inputParameters:
- name: workbook_id
in: body
type: string
description: "The Tableau workbook ID."
call: tableau.get-extract-refresh
with:
workbook_id: "{{workbook_id}}"
outputParameters:
- name: status
type: string
mapping: "$.extractRefreshes[0].status"
- name: completed_at
type: string
mapping: "$.extractRefreshes[0].completedAt"
consumes:
- type: http
namespace: tableau
baseUri: "https://pfizer.online.tableau.com/api/3.21"
authentication:
type: bearer
token: "$secrets.tableau_token"
resources:
- name: workbooks
path: "/sites/{{site_id}}/workbooks/{{workbook_id}}/refreshes"
inputParameters:
- name: workbook_id
in: path
operations:
- name: get-extract-refresh
method: GET
Manages infrastructure provisioning by creating ServiceNow change requests, triggering Terraform plans, and notifying the cloud team for Pfizer.
naftiko: "0.5"
info:
label: "Terraform Infrastructure Provisioning with Approval"
description: "Manages infrastructure provisioning by creating ServiceNow change requests, triggering Terraform plans, and notifying the cloud team for Pfizer."
tags:
- devops
- terraform
- servicenow
- cloud
capability:
exposes:
- type: mcp
namespace: cloud-ops
port: 8080
tools:
- name: provision-infrastructure
description: "Given infrastructure requirements, create a change request, generate a Terraform plan, and notify cloud engineering."
inputParameters:
- name: environment
in: body
type: string
description: "Target environment (dev, staging, production)."
- name: resource_type
in: body
type: string
description: "Type of resource to provision."
- name: requestor
in: body
type: string
description: "Name of the requestor."
steps:
- name: create-change
type: call
call: servicenow.create-change
with:
short_description: "Infra Provisioning: {{resource_type}} in {{environment}}"
category: "cloud_infrastructure"
- name: trigger-plan
type: call
call: github.trigger-workflow
with:
repo: "infrastructure"
workflow: "terraform-plan.yml"
- name: notify-cloud-team
type: call
call: msteams.send-message
with:
channel_id: "$secrets.cloud_eng_channel"
text: "Infra Request: {{resource_type}} in {{environment}} by {{requestor}}. Change: {{create-change.number}}. Terraform plan triggered."
consumes:
- type: http
namespace: servicenow
baseUri: "https://pfizer.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: github
baseUri: "https://api.github.com"
authentication:
type: bearer
token: "$secrets.github_token"
resources:
- name: workflows
path: "/repos/{{repo}}/actions/workflows/{{workflow}}/dispatches"
inputParameters:
- name: repo
in: path
- name: workflow
in: path
operations:
- name: trigger-workflow
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves the current lifecycle status of a document in Veeva Vault by document ID for Pfizer regulatory operations.
naftiko: "0.5"
info:
label: "Veeva Vault Document Status Lookup"
description: "Retrieves the current lifecycle status of a document in Veeva Vault by document ID for Pfizer regulatory operations."
tags:
- regulatory
- veeva-vault
- document-management
- lookup
capability:
exposes:
- type: mcp
namespace: regulatory-ops
port: 8080
tools:
- name: get-document-status
description: "Given a Veeva Vault document ID, return the lifecycle state, owner, and last modified date."
inputParameters:
- name: document_id
in: body
type: string
description: "The Veeva Vault document ID."
call: veeva.get-document
with:
document_id: "{{document_id}}"
outputParameters:
- name: lifecycle_state
type: string
mapping: "$.responseDetails.lifecycle__v"
- name: owner
type: string
mapping: "$.responseDetails.owner__v"
- name: last_modified
type: string
mapping: "$.responseDetails.last_modified_date__v"
consumes:
- type: http
namespace: veeva
baseUri: "https://pfizer.veevavault.com/api/v24.1"
authentication:
type: bearer
token: "$secrets.veeva_token"
resources:
- name: documents
path: "/objects/documents/{{document_id}}"
inputParameters:
- name: document_id
in: path
operations:
- name: get-document
method: GET
Orchestrates vendor qualification reviews by pulling vendor data from SAP, creating a ServiceNow assessment task, and notifying procurement for Pfizer.
naftiko: "0.5"
info:
label: "Vendor Qualification Review Orchestrator"
description: "Orchestrates vendor qualification reviews by pulling vendor data from SAP, creating a ServiceNow assessment task, and notifying procurement for Pfizer."
tags:
- procurement
- sap
- servicenow
- vendor-management
capability:
exposes:
- type: mcp
namespace: procurement-ops
port: 8080
tools:
- name: initiate-vendor-review
description: "Given a vendor number, retrieve vendor details from SAP, create an assessment task, and notify procurement."
inputParameters:
- name: vendor_number
in: body
type: string
description: "The SAP vendor number."
- name: review_type
in: body
type: string
description: "Type of qualification review (initial, periodic, for-cause)."
steps:
- name: get-vendor-data
type: call
call: sap.get-vendor
with:
vendor_number: "{{vendor_number}}"
- name: create-assessment
type: call
call: servicenow.create-incident
with:
short_description: "Vendor Qualification: {{get-vendor-data.SupplierName}} — {{review_type}}"
category: "vendor_management"
- name: notify-procurement
type: call
call: msteams.send-message
with:
channel_id: "$secrets.procurement_channel"
text: "Vendor Review initiated for {{get-vendor-data.SupplierName}} ({{vendor_number}}). Type: {{review_type}}. Task: {{create-assessment.number}}."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_BUSINESS_PARTNER"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: create-record
method: POST
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves employee absence and leave balance from Workday for Pfizer HR operations.
naftiko: "0.5"
info:
label: "Workday Absence Balance Lookup"
description: "Retrieves employee absence and leave balance from Workday for Pfizer HR operations."
tags:
- hr
- workday
- absence
- lookup
capability:
exposes:
- type: mcp
namespace: hr-absence
port: 8080
tools:
- name: get-absence-balance
description: "Given an employee ID, return the PTO balance, sick leave balance, and next scheduled absence."
inputParameters:
- name: employee_id
in: body
type: string
description: "The Workday employee ID."
call: workday.get-absence-balance
with:
employee_id: "{{employee_id}}"
outputParameters:
- name: pto_balance
type: string
mapping: "$.TimeOff.PTO_Balance"
- name: sick_balance
type: string
mapping: "$.TimeOff.Sick_Balance"
consumes:
- type: http
namespace: workday
baseUri: "https://wd5-services1.myworkday.com/ccx/service/pfizer/Absence_Management/v42.0"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: absences
path: "/workers/{{employee_id}}/absenceBalances"
inputParameters:
- name: employee_id
in: path
operations:
- name: get-absence-balance
method: GET
Retrieves compensation plan details for an employee from Workday for Pfizer HR total rewards operations.
naftiko: "0.5"
info:
label: "Workday Compensation Lookup"
description: "Retrieves compensation plan details for an employee from Workday for Pfizer HR total rewards operations."
tags:
- hr
- workday
- compensation
- lookup
capability:
exposes:
- type: mcp
namespace: hr-rewards
port: 8080
tools:
- name: get-compensation
description: "Given an employee ID, return the base pay, bonus target percentage, and compensation grade."
inputParameters:
- name: employee_id
in: body
type: string
description: "The Workday employee ID."
call: workday.get-compensation
with:
employee_id: "{{employee_id}}"
outputParameters:
- name: base_pay
type: string
mapping: "$.Compensation.Base_Pay"
- name: bonus_target
type: string
mapping: "$.Compensation.Bonus_Target_Percent"
- name: grade
type: string
mapping: "$.Compensation.Compensation_Grade"
consumes:
- type: http
namespace: workday
baseUri: "https://wd5-services1.myworkday.com/ccx/service/pfizer/Compensation/v42.0"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: compensation
path: "/workers/{{employee_id}}/compensationPlans"
inputParameters:
- name: employee_id
in: path
operations:
- name: get-compensation
method: GET
When an employee termination is processed in Workday, creates a ServiceNow offboarding ticket and notifies IT security in Microsoft Teams to begin access revocation.
naftiko: "0.5"
info:
label: "Workday Employee Offboarding Workflow"
description: "When an employee termination is processed in Workday, creates a ServiceNow offboarding ticket and notifies IT security in Microsoft Teams to begin access revocation."
tags:
- hr
- offboarding
- workday
- servicenow
- microsoft-teams
capability:
exposes:
- type: mcp
namespace: hr-offboarding
port: 8080
tools:
- name: trigger-offboarding
description: "Given a Workday worker ID and termination date, create a ServiceNow offboarding ticket and alert the IT security team in Teams."
inputParameters:
- name: worker_id
in: body
type: string
description: "The Workday worker ID of the departing employee."
- name: termination_date
in: body
type: string
description: "The employee's last day in YYYY-MM-DD format."
steps:
- name: get-employee
type: call
call: workday.get-worker
with:
worker_id: "{{worker_id}}"
- name: create-offboard-ticket
type: call
call: servicenow.create-incident
with:
short_description: "Offboarding: {{get-employee.full_name}} — last day {{termination_date}}"
category: "hr_offboarding"
assigned_group: "IT_Security"
- name: notify-it-security
type: call
call: msteams.send-message
with:
channel_id: "it-security-channel"
text: "Offboarding initiated for {{get-employee.full_name}} (last day: {{termination_date}}). SNOW: {{create-offboard-ticket.number}}. Begin access revocation."
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: "/pfizer/workers/{{worker_id}}"
inputParameters:
- name: worker_id
in: path
operations:
- name: get-worker
method: GET
- type: http
namespace: servicenow
baseUri: "https://pfizer.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.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves employee profile details from Workday by employee ID for Pfizer HR operations.
naftiko: "0.5"
info:
label: "Workday Employee Profile Lookup"
description: "Retrieves employee profile details from Workday by employee ID for Pfizer HR operations."
tags:
- hr
- workday
- employee
- lookup
capability:
exposes:
- type: mcp
namespace: hr-ops
port: 8080
tools:
- name: get-employee-profile
description: "Given a Workday employee ID, return the name, department, manager, and hire date."
inputParameters:
- name: employee_id
in: body
type: string
description: "The Workday employee ID."
call: workday.get-worker
with:
employee_id: "{{employee_id}}"
outputParameters:
- name: full_name
type: string
mapping: "$.Worker.Worker_Data.Personal_Data.Name_Data.Legal_Name.Name_Detail_Data.Formatted_Name"
- name: department
type: string
mapping: "$.Worker.Worker_Data.Organization_Data.Worker_Organization_Data[0].Organization_Data.Organization_Name"
- name: hire_date
type: string
mapping: "$.Worker.Worker_Data.Employment_Data.Worker_Status_Data.Hire_Date"
consumes:
- type: http
namespace: workday
baseUri: "https://wd5-services1.myworkday.com/ccx/service/pfizer/Human_Resources/v42.0"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: workers
path: "/workers/{{employee_id}}"
inputParameters:
- name: employee_id
in: path
operations:
- name: get-worker
method: GET
Exports the current active headcount and payroll summary by cost center from Workday and posts a digest to the HR finance Microsoft Teams channel.
naftiko: "0.5"
info:
label: "Workday Headcount and Payroll Snapshot"
description: "Exports the current active headcount and payroll summary by cost center from Workday and posts a digest to the HR finance Microsoft Teams channel."
tags:
- hr
- finance
- workday
- reporting
- microsoft-teams
- payroll
capability:
exposes:
- type: mcp
namespace: hr-finance-reporting
port: 8080
tools:
- name: get-payroll-snapshot
description: "Retrieve the active headcount and aggregated payroll cost by cost center from Workday and post the summary to the HR finance Teams channel."
inputParameters:
- name: as_of_date
in: body
type: string
description: "The snapshot date in YYYY-MM-DD format."
- name: teams_channel_id
in: body
type: string
description: "Teams channel ID for the HR finance snapshot."
steps:
- name: export-workers
type: call
call: workday.list-workers
with:
status: "active"
as_of_date: "{{as_of_date}}"
- name: post-snapshot
type: call
call: msteams.send-message
with:
channel_id: "{{teams_channel_id}}"
text: "Pfizer Headcount Snapshot ({{as_of_date}}): {{export-workers.total}} active employees. Total payroll cost: ${{export-workers.total_payroll}}."
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: "/pfizer/workers"
inputParameters:
- name: status
in: query
- name: as_of_date
in: query
operations:
- name: list-workers
method: GET
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Retrieves the status of a Workday job requisition by ID and returns its stage, hiring manager, and open headcount count for talent acquisition tracking.
naftiko: "0.5"
info:
label: "Workday Job Requisition Status Lookup"
description: "Retrieves the status of a Workday job requisition by ID and returns its stage, hiring manager, and open headcount count for talent acquisition tracking."
tags:
- hr
- recruiting
- workday
- lookup
- talent-acquisition
capability:
exposes:
- type: mcp
namespace: recruiting-lookup
port: 8080
tools:
- name: get-job-requisition
description: "Given a Workday job requisition ID, return the requisition stage, hiring manager name, target headcount, and filled positions."
inputParameters:
- name: requisition_id
in: body
type: string
description: "The Workday job requisition ID (e.g., 'JR-10045')."
call: workday.get-requisition
with:
requisition_id: "{{requisition_id}}"
outputParameters:
- name: stage
type: string
mapping: "$.jobRequisition.requisitionStatus"
- name: hiring_manager
type: string
mapping: "$.jobRequisition.hiringManager.descriptor"
- name: target_headcount
type: integer
mapping: "$.jobRequisition.targetHeadcount"
- name: filled_positions
type: integer
mapping: "$.jobRequisition.filledPositions"
consumes:
- type: http
namespace: workday
baseUri: "https://wd2-impl-services1.workday.com/ccx/api/v1"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: job-requisitions
path: "/pfizer/jobRequisitions/{{requisition_id}}"
inputParameters:
- name: requisition_id
in: path
operations:
- name: get-requisition
method: GET
Identifies overdue compliance training assignments in Workday and sends reminder notifications for Pfizer.
naftiko: "0.5"
info:
label: "Workday Learning Compliance Reminder"
description: "Identifies overdue compliance training assignments in Workday and sends reminder notifications for Pfizer."
tags:
- hr
- workday
- compliance
- training
capability:
exposes:
- type: mcp
namespace: hr-compliance
port: 8080
tools:
- name: send-compliance-reminders
description: "Given a compliance training program ID, find overdue assignments and send reminders."
inputParameters:
- name: program_id
in: body
type: string
description: "The Workday learning program ID."
- name: days_overdue
in: body
type: integer
description: "Minimum days overdue to trigger reminder."
steps:
- name: get-overdue
type: call
call: workday.get-overdue-training
with:
program_id: "{{program_id}}"
days_overdue: "{{days_overdue}}"
- name: send-reminder
type: call
call: msteams.send-message
with:
channel_id: "$secrets.hr_compliance_channel"
text: "Compliance Training Alert: {{get-overdue.count}} employees overdue for program {{program_id}} (>{{days_overdue}} days)."
consumes:
- type: http
namespace: workday
baseUri: "https://wd5-services1.myworkday.com/ccx/service/pfizer/Learning/v42.0"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: training
path: "/learningAssignments?overdue=true&program={{program_id}}"
inputParameters:
- name: program_id
in: query
operations:
- name: get-overdue-training
method: GET
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
When a new hire is created in Workday, opens a ServiceNow onboarding ticket, sends a Microsoft Teams welcome message, and creates a SharePoint document workspace.
naftiko: "0.5"
info:
label: "Workday New Hire Onboarding Orchestrator"
description: "When a new hire is created in Workday, opens a ServiceNow onboarding ticket, sends a Microsoft Teams welcome message, and creates a SharePoint document workspace."
tags:
- hr
- onboarding
- workday
- servicenow
- microsoft-teams
- sharepoint
capability:
exposes:
- type: mcp
namespace: hr-onboarding
port: 8080
tools:
- name: trigger-onboarding
description: "Given a Workday employee ID and start date, orchestrate Pfizer's onboarding sequence across ServiceNow, Microsoft Teams, and SharePoint."
inputParameters:
- name: worker_id
in: body
type: string
description: "The Workday worker ID for the new Pfizer hire."
- name: start_date
in: body
type: string
description: "The new hire's start date in YYYY-MM-DD format."
- name: site_id
in: body
type: string
description: "The SharePoint site ID for the onboarding document workspace."
steps:
- name: get-employee
type: call
call: workday.get-worker
with:
worker_id: "{{worker_id}}"
- name: create-snow-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: create-sharepoint-workspace
type: call
call: sharepoint.create-folder
with:
site_id: "{{site_id}}"
folder_path: "NewHires/{{get-employee.full_name}}_{{start_date}}"
- name: send-welcome
type: call
call: msteams.send-message
with:
channel_id: "hr-new-hires"
text: "Welcome to Pfizer, {{get-employee.full_name}}! Your onboarding ticket is {{create-snow-ticket.number}}. Start date: {{start_date}}."
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: "/pfizer/workers/{{worker_id}}"
inputParameters:
- name: worker_id
in: path
operations:
- name: get-worker
method: GET
- type: http
namespace: servicenow
baseUri: "https://pfizer.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"
authentication:
type: bearer
token: "$secrets.sharepoint_token"
resources:
- name: folders
path: "/sites/{{site_id}}/drive/root/children"
inputParameters:
- name: site_id
in: path
operations:
- name: create-folder
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Initiates a Pfizer performance review cycle in Workday for a given business unit and notifies managers in Microsoft Teams to begin annual employee reviews.
naftiko: "0.5"
info:
label: "Workday Performance Review Cycle Initiation"
description: "Initiates a Pfizer performance review cycle in Workday for a given business unit and notifies managers in Microsoft Teams to begin annual employee reviews."
tags:
- hr
- performance-management
- workday
- microsoft-teams
capability:
exposes:
- type: mcp
namespace: hr-performance
port: 8080
tools:
- name: initiate-review-cycle
description: "Given a Workday business unit code and review period, initiate the performance review cycle and send a Teams notification to all people managers to begin employee evaluations."
inputParameters:
- name: business_unit
in: body
type: string
description: "The Pfizer business unit code for the review cycle."
- name: review_period
in: body
type: string
description: "The performance review period (e.g., 'Annual-2025')."
- name: due_date
in: body
type: string
description: "Review completion deadline in YYYY-MM-DD format."
- name: manager_channel_id
in: body
type: string
description: "Teams channel ID for manager notifications."
steps:
- name: create-review-cycle
type: call
call: workday.create-review-cycle
with:
business_unit: "{{business_unit}}"
review_period: "{{review_period}}"
due_date: "{{due_date}}"
- name: notify-managers
type: call
call: msteams.send-message
with:
channel_id: "{{manager_channel_id}}"
text: "Performance Review Cycle '{{review_period}}' launched for {{business_unit}}. Please complete all evaluations in Workday by {{due_date}}. Cycle ID: {{create-review-cycle.cycle_id}}."
consumes:
- type: http
namespace: workday
baseUri: "https://wd2-impl-services1.workday.com/ccx/api/v1"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: review-cycles
path: "/pfizer/performanceReviews"
operations:
- name: create-review-cycle
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST
Processes new position requisitions by validating budget in SAP, creating the requisition in Workday, and notifying HR for Pfizer.
naftiko: "0.5"
info:
label: "Workday Position Requisition Approval Workflow"
description: "Processes new position requisitions by validating budget in SAP, creating the requisition in Workday, and notifying HR for Pfizer."
tags:
- hr
- workday
- sap
- hiring
capability:
exposes:
- type: mcp
namespace: hr-talent
port: 8080
tools:
- name: process-position-requisition
description: "Given requisition details, validate budget, create the position in Workday, and notify HR."
inputParameters:
- name: department
in: body
type: string
description: "The department requesting the position."
- name: job_title
in: body
type: string
description: "The job title."
- name: cost_center
in: body
type: string
description: "The SAP cost center."
- name: hiring_manager
in: body
type: string
description: "Name of the hiring manager."
steps:
- name: validate-budget
type: call
call: sap.check-budget
with:
cost_center: "{{cost_center}}"
amount_type: "headcount"
- name: create-requisition
type: call
call: workday.create-requisition
with:
department: "{{department}}"
job_title: "{{job_title}}"
hiring_manager: "{{hiring_manager}}"
- name: notify-hr
type: call
call: msteams.send-message
with:
channel_id: "$secrets.hr_recruiting_channel"
text: "New Position Requisition: {{job_title}} in {{department}}. Manager: {{hiring_manager}}. Budget: {{validate-budget.status}}. Workday Req: {{create-requisition.requisition_id}}."
consumes:
- type: http
namespace: sap
baseUri: "https://pfizer-s4.sap.com/sap/opu/odata/sap/API_BUDGET_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: records
path: "/"
operations:
- name: create-record
method: POST
- type: http
namespace: workday
baseUri: "https://wd5-services1.myworkday.com/ccx/service/pfizer/Recruiting/v42.0"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: requisitions
path: "/jobRequisitions"
operations:
- name: create-requisition
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msteams_token"
resources:
- name: messages
path: "/teams/{{channel_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: channel_id
in: path
operations:
- name: send-message
method: POST