Novartis Capabilities
Naftiko 0.5 capability definitions for Novartis - 100 capabilities showing integration workflows and service orchestrations.
Sort
Expand
Azure Data Factory Pipeline Failure Handler
▼
data-engineering azure-data-factory servicenow monitoring
Handles Azure Data Factory pipeline failures by creating a ServiceNow incident and notifying the data engineering team for Novartis.
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 Novartis."
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://novartis.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
Azure DevOps Build Status Lookup
▼
devops azure-devops ci-cd lookup
Retrieves the latest build status from Azure DevOps for a given pipeline in Novartis 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 Novartis 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/novartis"
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
Clinical Data Lock Orchestrator
▼
clinical-trials data-management snowflake veeva-vault
Orchestrates the clinical database lock process by verifying data completeness in Snowflake, updating status in Veeva Vault, and notifying stakeholders for Novartis.
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 Novartis."
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://novartis.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://novartis.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
Clinical Data Reconciliation Checker
▼
clinical-trials data-management veeva-vault snowflake
Reconciles clinical data between Veeva Vault and Snowflake, logs discrepancies in Jira, and alerts the data management team for Novartis.
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 Novartis."
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://novartis.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://novartis.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://novartis.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
Clinical Protocol Amendment Processor
▼
clinical-trials veeva-vault jira regulatory
Processes clinical protocol amendments by updating Veeva Vault, creating Jira tracking tasks, and notifying the clinical team for Novartis.
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 Novartis."
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://novartis.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://novartis.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
Clinical Safety Reporting SUSAR Handler
▼
drug-safety clinical-trials veeva-vault regulatory
Processes Suspected Unexpected Serious Adverse Reactions by logging in Veeva Vault, creating urgent ServiceNow cases, and alerting the DSMB for Novartis.
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 Novartis."
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://novartis.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://novartis.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
Clinical Site Monitoring Visit Scheduler
▼
clinical-trials veeva-vault jira scheduling
Creates monitoring visit schedules in Veeva Vault, assigns tasks in Jira, and notifies the CRA team for Novartis.
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 Novartis."
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://novartis.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://novartis.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
Clinical Trial Data Batch Upload to Veeva Vault
▼
regulatory clinical-trials veeva microsoft-teams
Uploads a clinical trial data package to Veeva Vault, triggering a document classification workflow and notifying the regulatory team via Microsoft Teams.
naftiko: "0.5"
info:
label: "Clinical Trial Data Batch Upload to Veeva Vault"
description: "Uploads a clinical trial data package to Veeva Vault, triggering a document classification workflow and notifying the regulatory team via Microsoft Teams."
tags:
- regulatory
- clinical-trials
- veeva
- microsoft-teams
capability:
exposes:
- type: mcp
namespace: regulatory-ops
port: 8080
tools:
- name: upload-clinical-trial-data
description: "Given a clinical trial ID and data package URL, upload the data package to Veeva Vault under the correct study folder and notify the regulatory affairs team via Microsoft Teams. Use when submitting clinical trial data for regulatory review."
inputParameters:
- name: trial_id
in: body
type: string
description: "The clinical trial identifier (e.g., 'CQGE130A2301')."
- name: vault_folder_id
in: body
type: string
description: "The Veeva Vault folder ID for this trial's documents."
- name: document_name
in: body
type: string
description: "Name of the document to create in Veeva Vault."
- name: teams_channel_id
in: body
type: string
description: "Microsoft Teams channel ID to notify regulatory team."
steps:
- name: create-vault-document
type: call
call: "veeva.create-document"
with:
folder_id: "{{vault_folder_id}}"
name: "{{document_name}}"
lifecycle: "Clinical_Study_Report_Lifecycle"
type: "Clinical_Study_Report"
- name: notify-regulatory-team
type: call
call: "msteams.post-channel-message"
with:
channel_id: "{{teams_channel_id}}"
text: "Clinical trial data uploaded to Veeva Vault for trial {{trial_id}}. Document ID: {{create-vault-document.document_id}}. Awaiting regulatory review."
consumes:
- type: http
namespace: veeva
baseUri: "https://novartis.veevavault.com/api/v24.1"
authentication:
type: bearer
token: "$secrets.veeva_token"
resources:
- name: documents
path: "/objects/documents"
operations:
- name: create-document
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msgraph_token"
resources:
- name: channel-messages
path: "/teams/{{team_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: team_id
in: path
- name: channel_id
in: path
operations:
- name: post-channel-message
method: POST
Clinical Trial Enrollment Status Reporter
▼
clinical-trials snowflake microsoft-teams reporting
Queries Snowflake for current enrollment figures by study, generates a summary, and posts to the clinical operations Teams channel for Novartis.
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 Novartis."
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://novartis.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
Cold Chain Temperature Excursion Handler
▼
supply-chain cold-chain quality sap
Handles cold chain temperature excursions by logging in SAP, creating a quality incident, and alerting logistics and quality teams for Novartis.
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 Novartis."
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://novartis-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://novartis.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
Concur Expense Report Approval Routing
▼
finance expense-management sap-concur microsoft-teams approval
Fetches pending SAP Concur expense reports exceeding the auto-approval limit and routes them to the appropriate manager for approval via Microsoft Teams.
naftiko: "0.5"
info:
label: "Concur Expense Report Approval Routing"
description: "Fetches pending SAP Concur expense reports exceeding the auto-approval limit and routes them to the appropriate manager for approval via Microsoft Teams."
tags:
- finance
- expense-management
- sap-concur
- microsoft-teams
- approval
capability:
exposes:
- type: mcp
namespace: expense-approvals
port: 8080
tools:
- name: route-expense-approval
description: "Given a Concur expense report ID and approver UPN, fetch report details and send an approval request via Microsoft Teams. Use for expense reports exceeding the auto-approval monetary threshold."
inputParameters:
- name: report_id
in: body
type: string
description: "The SAP Concur expense report ID."
- name: approver_upn
in: body
type: string
description: "The UPN (email) of the designated expense approver."
steps:
- name: get-expense-report
type: call
call: "concur.get-report"
with:
report_id: "{{report_id}}"
- name: notify-approver
type: call
call: "msteams.send-message"
with:
recipient_upn: "{{approver_upn}}"
text: "Expense Approval Required: Report {{report_id}} | Employee: {{get-expense-report.OwnerName}} | Amount: {{get-expense-report.Total}} {{get-expense-report.CurrencyCode}} | Please approve in SAP Concur."
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
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msgraph_token"
resources:
- name: mail
path: "/users/{{recipient_upn}}/sendMail"
inputParameters:
- name: recipient_upn
in: path
operations:
- name: send-message
method: POST
Confluence Regulatory Knowledge Search
▼
regulatory confluence knowledge-management search
Searches Novartis Confluence knowledge base for regulatory guidance documents by keyword.
naftiko: "0.5"
info:
label: "Confluence Regulatory Knowledge Search"
description: "Searches Novartis 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://novartis.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
Databricks ML Model Deployment Pipeline
▼
r-and-d databricks machine-learning deployment
Orchestrates ML model deployment by promoting a model in Databricks, updating the model registry, and notifying the data science team for Novartis.
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 Novartis."
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://novartis.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://novartis.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
Datadog Service Health Check
▼
monitoring datadog sre health-check
Retrieves the current health status of a monitored service from Datadog for Novartis SRE operations.
naftiko: "0.5"
info:
label: "Datadog Service Health Check"
description: "Retrieves the current health status of a monitored service from Datadog for Novartis 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
Document Control SOP Review Cycle Initiator
▼
quality document-control veeva-vault jira
Initiates periodic SOP review cycles by identifying documents due for review in Veeva Vault, creating Jira tasks, and notifying owners for Novartis.
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 Novartis."
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://novartis.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://novartis.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
Drug Safety Adverse Event Report Processor
▼
drug-safety pharmacovigilance servicenow compliance
Receives an adverse event report, creates a pharmacovigilance case in ServiceNow, and notifies the drug safety team via Teams for Novartis.
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 Novartis."
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://novartis.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
Employee Offboarding and Access Revocation
▼
hr offboarding workday okta servicenow
When a Workday termination event is recorded, suspends the Okta account, removes Microsoft 365 license, and creates a ServiceNow offboarding task.
naftiko: "0.5"
info:
label: "Employee Offboarding and Access Revocation"
description: "When a Workday termination event is recorded, suspends the Okta account, removes Microsoft 365 license, and creates a ServiceNow offboarding task."
tags:
- hr
- offboarding
- workday
- okta
- servicenow
capability:
exposes:
- type: mcp
namespace: hr-offboarding
port: 8080
tools:
- name: trigger-offboarding
description: "Given a Workday employee ID, revoke Okta access, remove Microsoft 365 license, and create a ServiceNow offboarding checklist task. Use when a Novartis employee separates from the company."
inputParameters:
- name: workday_employee_id
in: body
type: string
description: "The Workday worker ID of the departing employee."
- name: last_day
in: body
type: string
description: "Employee's last working day in ISO 8601 format (YYYY-MM-DD)."
steps:
- name: get-employee
type: call
call: "workday.get-worker"
with:
worker_id: "{{workday_employee_id}}"
- name: suspend-okta
type: call
call: "okta.suspend-user"
with:
user_id: "{{get-employee.okta_user_id}}"
- name: remove-m365-license
type: call
call: "msgraph.remove-license"
with:
user_id: "{{get-employee.azure_ad_id}}"
- name: create-offboarding-task
type: call
call: "servicenow.create-task"
with:
short_description: "Offboarding: {{get-employee.full_name}} — last day {{last_day}}"
category: "hr_offboarding"
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: "/novartis/workers/{{worker_id}}"
inputParameters:
- name: worker_id
in: path
operations:
- name: get-worker
method: GET
- type: http
namespace: okta
baseUri: "https://novartis.okta.com/api/v1"
authentication:
type: apikey
key: "Authorization"
value: "$secrets.okta_api_token"
placement: header
resources:
- name: user-suspend
path: "/users/{{user_id}}/lifecycle/suspend"
inputParameters:
- name: user_id
in: path
operations:
- name: suspend-user
method: POST
- type: http
namespace: msgraph
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msgraph_token"
resources:
- name: user-licenses
path: "/users/{{user_id}}/assignLicense"
inputParameters:
- name: user_id
in: path
operations:
- name: remove-license
method: POST
- type: http
namespace: servicenow
baseUri: "https://novartis.service-now.com/api/now"
authentication:
type: basic
username: "$secrets.servicenow_user"
password: "$secrets.servicenow_password"
resources:
- name: tasks
path: "/table/sc_task"
operations:
- name: create-task
method: POST
Employee Onboarding Orchestrator
▼
hr onboarding workday servicenow okta microsoft-teams
When a new hire is created in Workday, opens a ServiceNow onboarding ticket, provisions Okta access, and sends a Microsoft Teams welcome message to the new employee.
naftiko: "0.5"
info:
label: "Employee Onboarding Orchestrator"
description: "When a new hire is created in Workday, opens a ServiceNow onboarding ticket, provisions Okta access, and sends a Microsoft Teams welcome message to the new employee."
tags:
- hr
- onboarding
- workday
- servicenow
- okta
- microsoft-teams
capability:
exposes:
- type: mcp
namespace: hr-onboarding
port: 8080
tools:
- name: trigger-onboarding
description: "Given a Workday employee ID and start date, orchestrate the full onboarding sequence across ServiceNow, Okta, and Microsoft Teams. Use when a new employee joins Novartis globally."
inputParameters:
- name: workday_employee_id
in: body
type: string
description: "The Workday worker ID for the new hire."
- name: start_date
in: body
type: string
description: "The employee's start date in ISO 8601 format (YYYY-MM-DD)."
- name: cost_center
in: body
type: string
description: "The Workday cost center code for the new hire's department."
steps:
- name: get-employee
type: call
call: "workday.get-worker"
with:
worker_id: "{{workday_employee_id}}"
- name: open-onboarding-ticket
type: call
call: "servicenow.create-incident"
with:
category: "hr_onboarding"
short_description: "New hire onboarding: {{get-employee.full_name}}"
assigned_group: "IT_Onboarding"
- name: activate-okta-user
type: call
call: "okta.activate-user"
with:
user_id: "{{get-employee.okta_user_id}}"
- name: send-welcome
type: call
call: "msteams.send-message"
with:
recipient_upn: "{{get-employee.work_email}}"
text: "Welcome to Novartis, {{get-employee.first_name}}! Your IT onboarding ticket is {{open-onboarding-ticket.number}}."
consumes:
- type: http
namespace: workday
baseUri: "https://wd2-impl-services1.workday.com/ccx/api/v1"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: workers
path: "/novartis/workers/{{worker_id}}"
inputParameters:
- name: worker_id
in: path
operations:
- name: get-worker
method: GET
- type: http
namespace: servicenow
baseUri: "https://novartis.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: okta
baseUri: "https://novartis.okta.com/api/v1"
authentication:
type: apikey
key: "Authorization"
value: "$secrets.okta_api_token"
placement: header
resources:
- name: user-lifecycle
path: "/users/{{user_id}}/lifecycle/activate"
inputParameters:
- name: user_id
in: path
operations:
- name: activate-user
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msgraph_token"
resources:
- name: mail
path: "/users/{{recipient_upn}}/sendMail"
inputParameters:
- name: recipient_upn
in: path
operations:
- name: send-message
method: POST
Environmental Monitoring Alert Handler
▼
manufacturing quality sap environmental-monitoring
Processes environmental monitoring excursions in manufacturing by logging in SAP QM, creating a ServiceNow incident, and alerting quality for Novartis.
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 Novartis."
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://novartis-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://novartis.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
FDA Inspection Readiness Checklist Generator
▼
regulatory compliance sharepoint workday
Generates FDA inspection readiness checklists by pulling SOPs from SharePoint, checking training compliance in Workday, and creating Jira tracking for Novartis.
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 Novartis."
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://novartis.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/novartis/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://novartis.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
GitHub Actions GxP Validation Pipeline Trigger
▼
devops github-actions gxp validation
Triggers GxP validation pipelines in GitHub Actions, logs validation events in ServiceNow, and notifies the QA team for Novartis.
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 Novartis."
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://novartis.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
GitHub Repository Compliance Check
▼
devops github compliance security
Checks a GitHub repository for branch protection rules and required status checks for Novartis 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 Novartis 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
Global Headcount Snapshot Report
▼
hr workforce-planning workday reporting
Returns current headcount grouped by department, country, and cost center from Workday, used for workforce planning and executive reporting.
naftiko: "0.5"
info:
label: "Global Headcount Snapshot Report"
description: "Returns current headcount grouped by department, country, and cost center from Workday, used for workforce planning and executive reporting."
tags:
- hr
- workforce-planning
- workday
- reporting
capability:
exposes:
- type: mcp
namespace: hr-reporting
port: 8080
tools:
- name: get-headcount-snapshot
description: "Return a snapshot of active Novartis employees grouped by department, country, and cost center from Workday. Use for global workforce planning, executive headcount reviews, or compliance reporting."
call: "workday.list-workers"
outputParameters:
- name: employees
type: array
mapping: "$.data"
- name: total_count
type: number
mapping: "$.total"
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: "/novartis/workers"
operations:
- name: list-workers
method: GET
GxP System Change Approval Workflow
▼
compliance gxp servicenow veeva-vault
Manages GxP-validated system change requests by creating a ServiceNow change, logging in Veeva Vault audit trail, and notifying approvers for Novartis.
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 Novartis."
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://novartis.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://novartis.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
HCP Speaker Program Event Coordinator
▼
medical-affairs salesforce compliance events
Coordinates HCP speaker program events by creating events in Salesforce, logging compliance checks, and notifying medical affairs for Novartis.
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 Novartis."
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://novartis.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://novartis.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
HubSpot Contact to Salesforce Opportunity Promotion
▼
sales marketing hubspot salesforce lead-qualification
When a HubSpot contact reaches a qualified lead score, creates a corresponding Salesforce opportunity and assigns it to the correct sales rep.
naftiko: "0.5"
info:
label: "HubSpot Contact to Salesforce Opportunity Promotion"
description: "When a HubSpot contact reaches a qualified lead score, creates a corresponding Salesforce opportunity and assigns it to the correct sales rep."
tags:
- sales
- marketing
- hubspot
- salesforce
- lead-qualification
capability:
exposes:
- type: mcp
namespace: mql-to-opportunity
port: 8080
tools:
- name: promote-mql-to-opportunity
description: "Given a HubSpot contact ID and owning sales rep Salesforce user ID, fetch contact details and create a Salesforce opportunity for the MQL. Use when a marketing qualified lead reaches the sales handoff threshold."
inputParameters:
- name: hubspot_contact_id
in: body
type: string
description: "The HubSpot contact ID of the MQL."
- name: salesforce_owner_id
in: body
type: string
description: "The Salesforce user ID of the assigned sales rep."
steps:
- name: get-hubspot-contact
type: call
call: "hubspot.get-contact"
with:
contact_id: "{{hubspot_contact_id}}"
- name: create-salesforce-opportunity
type: call
call: "salesforce.create-opportunity"
with:
name: "{{get-hubspot-contact.company}} — Inbound MQL"
account_name: "{{get-hubspot-contact.company}}"
stage: "Prospecting"
close_date: "2026-06-30"
owner_id: "{{salesforce_owner_id}}"
consumes:
- type: http
namespace: hubspot
baseUri: "https://api.hubapi.com/crm/v3"
authentication:
type: bearer
token: "$secrets.hubspot_token"
resources:
- name: contacts
path: "/objects/contacts/{{contact_id}}"
inputParameters:
- name: contact_id
in: path
operations:
- name: get-contact
method: GET
- type: http
namespace: salesforce
baseUri: "https://novartis.my.salesforce.com/services/data/v58.0"
authentication:
type: bearer
token: "$secrets.salesforce_token"
resources:
- name: opportunities
path: "/sobjects/Opportunity"
operations:
- name: create-opportunity
method: POST
HubSpot Marketing Campaign Performance Digest
▼
marketing hubspot microsoft-teams reporting
Fetches HubSpot campaign email performance metrics and publishes a weekly digest to the marketing Microsoft Teams channel.
naftiko: "0.5"
info:
label: "HubSpot Marketing Campaign Performance Digest"
description: "Fetches HubSpot campaign email performance metrics and publishes a weekly digest to the marketing Microsoft Teams channel."
tags:
- marketing
- hubspot
- microsoft-teams
- reporting
capability:
exposes:
- type: mcp
namespace: marketing-reporting
port: 8080
tools:
- name: digest-campaign-performance
description: "Fetch HubSpot email campaign performance for a given campaign ID and post open rate, click rate, and unsubscribe metrics to the marketing Teams channel. Use for weekly marketing performance reviews."
inputParameters:
- name: campaign_id
in: body
type: string
description: "The HubSpot campaign ID to report on."
- name: teams_channel_id
in: body
type: string
description: "Microsoft Teams channel ID to post the digest to."
steps:
- name: get-campaign-metrics
type: call
call: "hubspot.get-campaign-stats"
with:
campaign_id: "{{campaign_id}}"
- name: post-digest
type: call
call: "msteams.post-channel-message"
with:
channel_id: "{{teams_channel_id}}"
text: "Campaign Performance: {{get-campaign-metrics.name}} | Sent: {{get-campaign-metrics.numSent}} | Open Rate: {{get-campaign-metrics.openRate}} | Click Rate: {{get-campaign-metrics.clickRate}}"
consumes:
- type: http
namespace: hubspot
baseUri: "https://api.hubapi.com/marketing/v3"
authentication:
type: bearer
token: "$secrets.hubspot_token"
resources:
- name: campaign-stats
path: "/emails/statistics/list"
inputParameters:
- name: campaign_id
in: query
operations:
- name: get-campaign-stats
method: GET
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msgraph_token"
resources:
- name: channel-messages
path: "/teams/{{team_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: team_id
in: path
- name: channel_id
in: path
operations:
- name: post-channel-message
method: POST
IT Security Vulnerability Remediation Tracker
▼
security servicenow compliance vulnerability-management
Tracks vulnerability remediation by pulling scan results, creating ServiceNow tickets, and reporting to the CISO dashboard for Novartis.
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 Novartis."
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://novartis.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
Jira Clinical Issue Status Lookup
▼
clinical-trials jira project-management lookup
Retrieves the status and details of a Jira issue by key for Novartis 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 Novartis 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://novartis.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
Laboratory Instrument Calibration Tracker
▼
r-and-d quality sap laboratory
Tracks laboratory instrument calibration schedules by querying SAP PM, creating ServiceNow work orders, and notifying lab managers for Novartis.
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 Novartis."
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://novartis-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://novartis.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
LinkedIn Employer Brand Campaign Publisher
▼
marketing social linkedin slack
Publishes a Novartis employer brand post to the LinkedIn company page and reports the publication to the corporate communications Slack channel.
naftiko: "0.5"
info:
label: "LinkedIn Employer Brand Campaign Publisher"
description: "Publishes a Novartis employer brand post to the LinkedIn company page and reports the publication to the corporate communications Slack channel."
tags:
- marketing
- social
- linkedin
- slack
capability:
exposes:
- type: mcp
namespace: brand-publishing
port: 8080
tools:
- name: publish-employer-brand-post
description: "Given post content, publish a Novartis employer brand post to the LinkedIn company page and notify the #corporate-comms Slack channel. Use for employer branding campaigns, drug approval announcements, or recruitment marketing."
inputParameters:
- name: post_text
in: body
type: string
description: "The text content of the LinkedIn employer brand post."
- name: visibility
in: body
type: string
description: "Post visibility setting: 'PUBLIC' or 'CONNECTIONS'."
steps:
- name: create-post
type: call
call: "linkedin.create-share"
with:
text: "{{post_text}}"
visibility: "{{visibility}}"
- name: notify-comms
type: call
call: "slack.post-message"
with:
channel: "corporate-comms"
text: "LinkedIn post published: Activity ID {{create-post.activity_id}}"
consumes:
- type: http
namespace: linkedin
baseUri: "https://api.linkedin.com/v2"
authentication:
type: bearer
token: "$secrets.linkedin_access_token"
resources:
- name: shares
path: "/ugcPosts"
operations:
- name: create-share
method: POST
- type: http
namespace: slack
baseUri: "https://slack.com/api"
authentication:
type: bearer
token: "$secrets.slack_bot_token"
resources:
- name: messages
path: "/chat.postMessage"
operations:
- name: post-message
method: POST
LinkedIn Talent Pipeline for Medical Science Liaisons
▼
hr linkedin workday talent-acquisition
Sources MSL candidates from LinkedIn, creates profiles in Workday recruiting, and notifies the talent acquisition team for Novartis.
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 Novartis."
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/novartis/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
Manufacturing Deviation Handler
▼
manufacturing quality servicenow sap
Processes manufacturing deviations by creating a ServiceNow incident, logging in SAP QM, and notifying quality assurance for Novartis.
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 Novartis."
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://novartis.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://novartis-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
Medical Information Request Handler
▼
medical-affairs salesforce knowledge-management compliance
Processes medical information requests by logging in Salesforce, searching the knowledge base, and notifying the medical affairs team for Novartis.
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 Novartis."
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://novartis.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://novartis.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
Okta Access Certification Campaign Launcher
▼
security okta servicenow compliance
Launches periodic access certification campaigns by pulling user data from Okta, creating review tasks, and notifying managers for Novartis.
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 Novartis."
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://novartis.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://novartis.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
Okta Privileged Access Quarterly Review
▼
identity security okta confluence access-review
Generates a list of users with privileged Okta group memberships and publishes a quarterly access review report to Confluence for the IT security team.
naftiko: "0.5"
info:
label: "Okta Privileged Access Quarterly Review"
description: "Generates a list of users with privileged Okta group memberships and publishes a quarterly access review report to Confluence for the IT security team."
tags:
- identity
- security
- okta
- confluence
- access-review
capability:
exposes:
- type: mcp
namespace: privileged-access-review
port: 8080
tools:
- name: run-privileged-access-review
description: "List all Okta users in privileged admin groups and publish a quarterly review report to Confluence. Use for SOX or ISO 27001 access certification cycles."
inputParameters:
- name: privileged_group_ids
in: body
type: string
description: "Comma-separated list of Okta group IDs representing privileged access groups."
- name: confluence_space_key
in: body
type: string
description: "Confluence space key for the access review report."
- name: confluence_parent_id
in: body
type: string
description: "Confluence parent page ID for the quarterly review."
steps:
- name: list-privileged-users
type: call
call: "okta.list-group-users"
with:
group_id: "{{privileged_group_ids}}"
- name: publish-report
type: call
call: "confluence.create-page"
with:
space_key: "{{confluence_space_key}}"
parent_page_id: "{{confluence_parent_id}}"
title: "Quarterly Privileged Access Review"
content: "Privileged Okta group membership report for quarterly access certification. Review and certify or revoke each entry."
consumes:
- type: http
namespace: okta
baseUri: "https://novartis.okta.com/api/v1"
authentication:
type: apikey
key: "Authorization"
value: "$secrets.okta_api_token"
placement: header
resources:
- name: group-members
path: "/groups/{{group_id}}/users"
inputParameters:
- name: group_id
in: path
operations:
- name: list-group-users
method: GET
- type: http
namespace: confluence
baseUri: "https://novartis.atlassian.net/wiki/rest/api"
authentication:
type: basic
username: "$secrets.confluence_user"
password: "$secrets.confluence_api_token"
resources:
- name: pages
path: "/content"
operations:
- name: create-page
method: POST
Okta User Status Lookup
▼
security okta identity lookup
Retrieves the current status and profile of an Okta user by login email for Novartis 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 Novartis 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://novartis.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
Patient Assistance Program Enrollment Processor
▼
commercial salesforce patient-services compliance
Processes patient assistance program enrollments by creating cases in Salesforce, verifying eligibility, and notifying patient services for Novartis.
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 Novartis."
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://novartis.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://novartis.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
Pharmacovigilance Signal Detection Reporter
▼
drug-safety pharmacovigilance snowflake analytics
Runs pharmacovigilance signal detection queries in Snowflake, generates summary reports, and alerts the safety review board for Novartis.
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 Novartis."
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://novartis.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://novartis.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
Power BI Dataset Refresh Status
▼
analytics power-bi reporting lookup
Checks the last refresh status of a Power BI dataset for Novartis analytics operations.
naftiko: "0.5"
info:
label: "Power BI Dataset Refresh Status"
description: "Checks the last refresh status of a Power BI dataset for Novartis 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
Product Recall Coordination Workflow
▼
quality product-recall salesforce sap
Coordinates product recall activities by creating cases in Salesforce, notifying logistics via SAP, and alerting leadership for Novartis.
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 Novartis."
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://novartis.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://novartis-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
R&D Compound Pipeline Dashboard Refresh
▼
r-and-d snowflake power-bi analytics
Refreshes the R&D pipeline dashboard by pulling compound status from Snowflake, updating Power BI, and notifying R&D leadership for Novartis.
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 Novartis."
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://novartis.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
Real-World Evidence Data Ingestion Pipeline
▼
r-and-d real-world-evidence snowflake data-engineering
Orchestrates RWE data ingestion from external sources into Snowflake, validates data quality, and notifies the HEOR team for Novartis.
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 Novartis."
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://novartis.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
Regulatory Submission Deadline Reminder
▼
regulatory veeva microsoft-teams compliance
Queries Veeva Vault for regulatory documents approaching their submission deadlines and sends reminders to the regulatory affairs team via Microsoft Teams.
naftiko: "0.5"
info:
label: "Regulatory Submission Deadline Reminder"
description: "Queries Veeva Vault for regulatory documents approaching their submission deadlines and sends reminders to the regulatory affairs team via Microsoft Teams."
tags:
- regulatory
- veeva
- microsoft-teams
- compliance
capability:
exposes:
- type: mcp
namespace: regulatory-reminders
port: 8080
tools:
- name: send-submission-deadline-reminders
description: "Query Veeva Vault for regulatory documents with submission deadlines within the next 14 days and notify the regulatory affairs Microsoft Teams channel. Use to prevent missed submission deadlines."
inputParameters:
- name: days_ahead
in: body
type: integer
description: "Number of days ahead to look for upcoming deadlines (e.g., 14)."
- name: teams_channel_id
in: body
type: string
description: "Microsoft Teams channel ID for the regulatory affairs team."
steps:
- name: query-upcoming-submissions
type: call
call: "veeva.query-documents"
with:
query: "SELECT id, name__v, submission_deadline__c, lifecycle_state__v FROM documents WHERE submission_deadline__c BETWEEN today() AND today()+{{days_ahead}} AND lifecycle_state__v != 'Approved'"
- name: notify-regulatory
type: call
call: "msteams.post-channel-message"
with:
channel_id: "{{teams_channel_id}}"
text: "Regulatory Deadline Alert: {{query-upcoming-submissions.responseDetails.total}} documents have submission deadlines within the next {{days_ahead}} days. Please review in Veeva Vault."
consumes:
- type: http
namespace: veeva
baseUri: "https://novartis.veevavault.com/api/v24.1"
authentication:
type: bearer
token: "$secrets.veeva_token"
resources:
- name: documents-query
path: "/query"
inputParameters:
- name: query
in: query
operations:
- name: query-documents
method: GET
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msgraph_token"
resources:
- name: channel-messages
path: "/teams/{{team_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: team_id
in: path
- name: channel_id
in: path
operations:
- name: post-channel-message
method: POST
Regulatory Submission Deadline Tracker
▼
regulatory veeva-vault jira compliance
Queries Veeva Vault for upcoming regulatory submission deadlines, creates Jira tracking tickets, and alerts the regulatory affairs team for Novartis.
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 Novartis."
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://novartis.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://novartis.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
Salesforce Commercial Territory Realignment Orchestrator
▼
commercial salesforce workday territory-management
Orchestrates commercial territory realignment by updating Salesforce territories, adjusting Workday reporting, and notifying the commercial team for Novartis.
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 Novartis."
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://novartis.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/novartis/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
Salesforce CRM Lead to HubSpot Sync
▼
sales marketing salesforce hubspot lead-management
Syncs a newly qualified Salesforce lead to HubSpot CRM for marketing automation follow-up, enriching the contact with lead source and qualification data.
naftiko: "0.5"
info:
label: "Salesforce CRM Lead to HubSpot Sync"
description: "Syncs a newly qualified Salesforce lead to HubSpot CRM for marketing automation follow-up, enriching the contact with lead source and qualification data."
tags:
- sales
- marketing
- salesforce
- hubspot
- lead-management
capability:
exposes:
- type: mcp
namespace: lead-sync
port: 8080
tools:
- name: sync-lead-to-hubspot
description: "Given a Salesforce lead ID, fetch lead details and create or update the corresponding HubSpot contact with lead source, qualification status, and owner info. Use when a lead is qualified in Salesforce and needs to enter HubSpot nurture workflows."
inputParameters:
- name: salesforce_lead_id
in: body
type: string
description: "The Salesforce lead ID to sync (18-character SFDC ID)."
steps:
- name: get-salesforce-lead
type: call
call: "salesforce.get-lead"
with:
lead_id: "{{salesforce_lead_id}}"
- name: upsert-hubspot-contact
type: call
call: "hubspot.upsert-contact"
with:
email: "{{get-salesforce-lead.Email}}"
firstname: "{{get-salesforce-lead.FirstName}}"
lastname: "{{get-salesforce-lead.LastName}}"
company: "{{get-salesforce-lead.Company}}"
lead_source: "{{get-salesforce-lead.LeadSource}}"
consumes:
- type: http
namespace: salesforce
baseUri: "https://novartis.my.salesforce.com/services/data/v58.0"
authentication:
type: bearer
token: "$secrets.salesforce_token"
resources:
- name: leads
path: "/sobjects/Lead/{{lead_id}}"
inputParameters:
- name: lead_id
in: path
operations:
- name: get-lead
method: GET
- type: http
namespace: hubspot
baseUri: "https://api.hubapi.com/crm/v3"
authentication:
type: bearer
token: "$secrets.hubspot_token"
resources:
- name: contacts
path: "/objects/contacts"
operations:
- name: upsert-contact
method: POST
Salesforce HCP Account Lookup
▼
commercial salesforce hcp lookup
Retrieves healthcare provider account details from Salesforce CRM by account ID for Novartis commercial operations.
naftiko: "0.5"
info:
label: "Salesforce HCP Account Lookup"
description: "Retrieves healthcare provider account details from Salesforce CRM by account ID for Novartis 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://novartis.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
Salesforce Key Opinion Leader Engagement Tracker
▼
medical-affairs salesforce snowflake analytics
Tracks KOL engagement activities by pulling data from Salesforce, summarizing in Snowflake, and reporting to medical affairs for Novartis.
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 Novartis."
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://novartis.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://novartis.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
Salesforce Opportunity Win/Loss Analysis Digest
▼
sales crm salesforce microsoft-teams reporting
Fetches closed Salesforce opportunities from the past 30 days, categorizes by win/loss, and publishes a sales performance digest to the revenue leadership Microsoft Teams channel.
naftiko: "0.5"
info:
label: "Salesforce Opportunity Win/Loss Analysis Digest"
description: "Fetches closed Salesforce opportunities from the past 30 days, categorizes by win/loss, and publishes a sales performance digest to the revenue leadership Microsoft Teams channel."
tags:
- sales
- crm
- salesforce
- microsoft-teams
- reporting
capability:
exposes:
- type: mcp
namespace: sales-reporting
port: 8080
tools:
- name: digest-win-loss-analysis
description: "Query closed Salesforce opportunities from the past 30 days, compute win rate by territory and product line, and post the digest to the revenue leadership Teams channel. Use for monthly sales reviews."
inputParameters:
- name: teams_channel_id
in: body
type: string
description: "Microsoft Teams channel ID for revenue leadership."
- name: territory
in: body
type: string
description: "Salesforce territory to filter results by (e.g., 'EMEA', 'APAC')."
steps:
- name: query-closed-opportunities
type: call
call: "salesforce.query-opportunities"
with:
soql: "SELECT Name, StageName, Amount, CloseDate, Territory2.Name FROM Opportunity WHERE CloseDate = LAST_N_DAYS:30 AND StageName IN ('Closed Won', 'Closed Lost') AND Territory2.Name = '{{territory}}'"
- name: post-digest
type: call
call: "msteams.post-channel-message"
with:
channel_id: "{{teams_channel_id}}"
text: "Sales Win/Loss Digest (Last 30 Days) — Territory: {{territory}} | Total Closed: {{query-closed-opportunities.totalSize}} opportunities. Review breakdown in Salesforce."
consumes:
- type: http
namespace: salesforce
baseUri: "https://novartis.my.salesforce.com/services/data/v58.0"
authentication:
type: bearer
token: "$secrets.salesforce_token"
resources:
- name: opportunity-query
path: "/query"
inputParameters:
- name: q
in: query
operations:
- name: query-opportunities
method: GET
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msgraph_token"
resources:
- name: channel-messages
path: "/teams/{{team_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: team_id
in: path
- name: channel_id
in: path
operations:
- name: post-channel-message
method: POST
SAP Ariba Contract Renewal Workflow
▼
procurement sap-ariba servicenow contract-management
Manages contract renewal workflows by checking expiring contracts in SAP Ariba, creating ServiceNow tasks, and notifying procurement for Novartis.
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 Novartis."
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/novartis"
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://novartis.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
SAP Ariba Purchase Requisition Approval
▼
procurement sap-ariba microsoft-teams approval
Fetches a pending SAP Ariba purchase requisition and routes it to the designated approver via Microsoft Teams with a direct approval link.
naftiko: "0.5"
info:
label: "SAP Ariba Purchase Requisition Approval"
description: "Fetches a pending SAP Ariba purchase requisition and routes it to the designated approver via Microsoft Teams with a direct approval link."
tags:
- procurement
- sap-ariba
- microsoft-teams
- approval
capability:
exposes:
- type: mcp
namespace: ariba-approvals
port: 8080
tools:
- name: route-requisition-approval
description: "Given an SAP Ariba requisition ID and approver UPN, fetch requisition details and send an approval notification via Microsoft Teams. Use when a purchase requisition exceeds the auto-approve threshold."
inputParameters:
- name: requisition_id
in: body
type: string
description: "The SAP Ariba purchase requisition ID."
- name: approver_upn
in: body
type: string
description: "The UPN (email) of the designated approver."
steps:
- name: get-requisition
type: call
call: "ariba.get-requisition"
with:
req_id: "{{requisition_id}}"
- name: notify-approver
type: call
call: "msteams.send-message"
with:
recipient_upn: "{{approver_upn}}"
text: "Approval Required: Purchase Requisition {{requisition_id}} | Description: {{get-requisition.description}} | Amount: {{get-requisition.totalCost}} {{get-requisition.currency}} | Please approve in SAP Ariba."
consumes:
- type: http
namespace: ariba
baseUri: "https://openapi.ariba.com/api/purchase-req/v1"
authentication:
type: apikey
key: "apiKey"
value: "$secrets.ariba_api_key"
placement: query
resources:
- name: requisitions
path: "/prod/requisitions/{{req_id}}"
inputParameters:
- name: req_id
in: path
operations:
- name: get-requisition
method: GET
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msgraph_token"
resources:
- name: mail
path: "/users/{{recipient_upn}}/sendMail"
inputParameters:
- name: recipient_upn
in: path
operations:
- name: send-message
method: POST
SAP Batch Genealogy Lookup
▼
manufacturing sap batch-tracking quality
Retrieves batch genealogy and traceability data from SAP for a given batch number in Novartis 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 Novartis 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://novartis-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
SAP Budget Variance Alert
▼
finance sap slack budget-management
Queries SAP cost center actuals versus budget for the current period and sends a Slack alert when variance exceeds the configured threshold.
naftiko: "0.5"
info:
label: "SAP Budget Variance Alert"
description: "Queries SAP cost center actuals versus budget for the current period and sends a Slack alert when variance exceeds the configured threshold."
tags:
- finance
- sap
- slack
- budget-management
capability:
exposes:
- type: mcp
namespace: budget-monitoring
port: 8080
tools:
- name: check-budget-variance
description: "Given a SAP cost center and variance threshold percentage, fetch actual vs. budget spend and post an alert to Slack if the threshold is exceeded. Use for monthly budget compliance monitoring."
inputParameters:
- name: cost_center
in: body
type: string
description: "The SAP cost center to check (e.g., 'CC-1042')."
- name: fiscal_period
in: body
type: string
description: "The fiscal period in YYYY/MM format (e.g., '2026/03')."
- name: variance_threshold_pct
in: body
type: number
description: "Variance percentage threshold to trigger alert (e.g., 10 for 10%)."
- name: slack_channel
in: body
type: string
description: "Slack channel for budget variance alerts."
steps:
- name: get-cost-center-actuals
type: call
call: "sap.get-cost-center-report"
with:
cost_center: "{{cost_center}}"
fiscal_period: "{{fiscal_period}}"
- name: post-variance-alert
type: call
call: "slack.post-message"
with:
channel: "{{slack_channel}}"
text: "Budget Variance Alert: Cost Center {{cost_center}} for period {{fiscal_period}} — actual vs. budget variance detected. Please review in SAP."
consumes:
- type: http
namespace: sap
baseUri: "https://novartis-s4.sap.com/sap/opu/odata/sap/API_COSTCENTER_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: cost-center-reports
path: "/A_CostCenterActuals"
inputParameters:
- name: cost_center
in: query
- name: fiscal_period
in: query
operations:
- name: get-cost-center-report
method: GET
outputRawFormat: xml
- type: http
namespace: slack
baseUri: "https://slack.com/api"
authentication:
type: bearer
token: "$secrets.slack_bot_token"
resources:
- name: messages
path: "/chat.postMessage"
operations:
- name: post-message
method: POST
SAP Concur Travel Policy Compliance Checker
▼
finance sap-concur compliance audit
Checks travel expense reports for policy violations, creates audit findings in ServiceNow, and notifies finance for Novartis.
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 Novartis."
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://novartis.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
SAP Cost Center Budget Variance Reporter
▼
finance sap budgeting reporting
Reports cost center budget variances from SAP, creates finance review tasks, and notifies the finance team for Novartis.
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 Novartis."
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://novartis-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://novartis.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
SAP Cost Element Lookup
▼
finance sap controlling lookup
Retrieves cost element master data from SAP for Novartis finance and controlling operations.
naftiko: "0.5"
info:
label: "SAP Cost Element Lookup"
description: "Retrieves cost element master data from SAP for Novartis 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://novartis-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
SAP Delivery Document Lookup
▼
logistics sap delivery lookup
Retrieves outbound delivery document details from SAP by delivery number for Novartis logistics operations.
naftiko: "0.5"
info:
label: "SAP Delivery Document Lookup"
description: "Retrieves outbound delivery document details from SAP by delivery number for Novartis 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://novartis-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
SAP Goods Receipt and Quality Release
▼
supply-chain sap quality warehouse
Processes goods receipt in SAP, triggers quality inspection, and notifies the warehouse team upon completion for Novartis.
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 Novartis."
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://novartis-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
SAP Inventory Stock Lookup
▼
supply-chain sap inventory manufacturing
Retrieves current inventory stock levels from SAP for a material at a given plant for Novartis 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 Novartis 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://novartis-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
SAP Invoice Processing and Approval
▼
finance accounts-payable sap microsoft-teams approval
Fetches a vendor invoice from SAP, checks for three-way match against the PO, and routes the invoice to the correct approver via Microsoft Teams.
naftiko: "0.5"
info:
label: "SAP Invoice Processing and Approval"
description: "Fetches a vendor invoice from SAP, checks for three-way match against the PO, and routes the invoice to the correct approver via Microsoft Teams."
tags:
- finance
- accounts-payable
- sap
- microsoft-teams
- approval
capability:
exposes:
- type: mcp
namespace: invoice-ops
port: 8080
tools:
- name: process-invoice-approval
description: "Given a SAP invoice number and approver UPN, retrieve invoice and PO match details from SAP and send an approval request to the approver via Microsoft Teams. Use for accounts payable exception handling."
inputParameters:
- name: invoice_number
in: body
type: string
description: "The SAP invoice document number."
- name: approver_upn
in: body
type: string
description: "The UPN (email) of the designated invoice approver."
steps:
- name: get-invoice
type: call
call: "sap.get-invoice"
with:
invoice_number: "{{invoice_number}}"
- name: notify-approver
type: call
call: "msteams.send-message"
with:
recipient_upn: "{{approver_upn}}"
text: "Invoice Approval Required: {{invoice_number}} | Vendor: {{get-invoice.SupplierName}} | Amount: {{get-invoice.DocumentAmount}} {{get-invoice.DocumentCurrency}} | Please approve in SAP."
consumes:
- type: http
namespace: sap
baseUri: "https://novartis-s4.sap.com/sap/opu/odata/sap/API_SUPPLIERINVOICE_PROCESS_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: supplier-invoices
path: "/A_SupplierInvoice('{{invoice_number}}')"
inputParameters:
- name: invoice_number
in: path
operations:
- name: get-invoice
method: GET
outputRawFormat: xml
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msgraph_token"
resources:
- name: mail
path: "/users/{{recipient_upn}}/sendMail"
inputParameters:
- name: recipient_upn
in: path
operations:
- name: send-message
method: POST
SAP Invoice Three-Way Match Validator
▼
finance sap accounts-payable compliance
Validates invoices by performing three-way matching in SAP, logs exceptions in ServiceNow, and notifies accounts payable for Novartis.
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 Novartis."
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://novartis-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://novartis.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
SAP Material Master Lookup
▼
manufacturing sap supply-chain lookup
Retrieves material master data from SAP S/4HANA by material number for Novartis 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 Novartis 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://novartis-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
SAP MRP Run Exception Handler
▼
supply-chain sap planning manufacturing
Handles MRP run exceptions from SAP by creating supply chain alerts, logging in ServiceNow, and notifying the planning team for Novartis.
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 Novartis."
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://novartis.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
SAP Planned Maintenance Order Creator
▼
manufacturing sap maintenance servicenow
Creates planned maintenance orders in SAP for manufacturing equipment, schedules in ServiceNow, and notifies the maintenance team for Novartis.
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 Novartis."
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://novartis-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://novartis.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
SAP Production Order Status Lookup
▼
manufacturing sap production lookup
Retrieves production order status and details from SAP for Novartis manufacturing operations.
naftiko: "0.5"
info:
label: "SAP Production Order Status Lookup"
description: "Retrieves production order status and details from SAP for Novartis 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://novartis-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
SAP Purchase Order Lookup
▼
finance procurement sap
Looks up a SAP S/4HANA purchase order by number and returns header status, vendor, and line item totals for finance and procurement teams.
naftiko: "0.5"
info:
label: "SAP Purchase Order Lookup"
description: "Looks up a SAP S/4HANA purchase order by number and returns header status, vendor, and line item totals for finance and procurement teams."
tags:
- finance
- procurement
- sap
capability:
exposes:
- type: mcp
namespace: procurement
port: 8080
tools:
- name: get-purchase-order
description: "Look up a SAP S/4HANA purchase order by PO number. Returns header status, vendor name, total value, currency, and open line item count. Use for procurement approvals or supplier payment queries."
inputParameters:
- name: po_number
in: body
type: string
description: "The SAP purchase order number (e.g., '4500012345')."
call: "sap.get-po"
with:
po_number: "{{po_number}}"
outputParameters:
- name: status
type: string
mapping: "$.d.OverallStatus"
- name: vendor
type: string
mapping: "$.d.Supplier.CompanyName"
- name: total_value
type: string
mapping: "$.d.TotalAmount"
- name: currency
type: string
mapping: "$.d.TransactionCurrency"
consumes:
- type: http
namespace: sap
baseUri: "https://novartis-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
outputRawFormat: xml
SAP Quality Inspection Lot Lookup
▼
quality sap manufacturing inspection
Retrieves quality inspection lot details from SAP for Novartis quality assurance operations.
naftiko: "0.5"
info:
label: "SAP Quality Inspection Lot Lookup"
description: "Retrieves quality inspection lot details from SAP for Novartis 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://novartis-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
SAP S/4HANA Financial Period Close Checklist
▼
finance sap period-close microsoft-teams reporting
Generates a financial period close checklist in SAP, verifies all journal entries are posted, and sends the period close confirmation to the CFO team via Microsoft Teams.
naftiko: "0.5"
info:
label: "SAP S/4HANA Financial Period Close Checklist"
description: "Generates a financial period close checklist in SAP, verifies all journal entries are posted, and sends the period close confirmation to the CFO team via Microsoft Teams."
tags:
- finance
- sap
- period-close
- microsoft-teams
- reporting
capability:
exposes:
- type: mcp
namespace: period-close
port: 8080
tools:
- name: run-period-close-checklist
description: "Verify SAP journal entry completeness for a fiscal period, fetch unposted entries count, and send the period close status summary to the CFO Microsoft Teams channel. Use at month-end and quarter-end close."
inputParameters:
- name: company_code
in: body
type: string
description: "SAP company code for the entity (e.g., '1000' for Novartis AG)."
- name: fiscal_year
in: body
type: string
description: "Fiscal year in YYYY format."
- name: fiscal_period
in: body
type: string
description: "Fiscal period number (01-12)."
- name: teams_channel_id
in: body
type: string
description: "Microsoft Teams channel ID for the CFO finance team."
steps:
- name: get-gl-entries
type: call
call: "sap.get-period-gl-entries"
with:
company_code: "{{company_code}}"
fiscal_year: "{{fiscal_year}}"
fiscal_period: "{{fiscal_period}}"
- name: notify-cfo-team
type: call
call: "msteams.post-channel-message"
with:
channel_id: "{{teams_channel_id}}"
text: "Period Close Status: {{company_code}} | FY{{fiscal_year}} Period {{fiscal_period}} | GL entries retrieved: {{get-gl-entries.count}}. Please verify all postings are complete before closing the period."
consumes:
- type: http
namespace: sap
baseUri: "https://novartis-s4.sap.com/sap/opu/odata/sap/API_JOURNALENTRYITEMBASIC_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: journal-entry-items
path: "/A_JournalEntryItem"
inputParameters:
- name: company_code
in: query
- name: fiscal_year
in: query
- name: fiscal_period
in: query
operations:
- name: get-period-gl-entries
method: GET
outputRawFormat: xml
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msgraph_token"
resources:
- name: channel-messages
path: "/teams/{{team_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: team_id
in: path
- name: channel_id
in: path
operations:
- name: post-channel-message
method: POST
SAP Transport Management Shipment Tracker
▼
supply-chain sap salesforce logistics
Tracks outbound shipments in SAP TM, updates delivery status in Salesforce, and notifies the distribution team for Novartis.
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 Novartis."
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://novartis-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://novartis.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
SAP Vendor Master Lookup
▼
procurement sap vendor-management lookup
Retrieves vendor master data from SAP S/4HANA by vendor number for Novartis procurement operations.
naftiko: "0.5"
info:
label: "SAP Vendor Master Lookup"
description: "Retrieves vendor master data from SAP S/4HANA by vendor number for Novartis 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://novartis-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
SAP Warehouse Capacity Planning Alert
▼
supply-chain sap warehouse capacity-planning
Monitors warehouse capacity levels in SAP, creates planning alerts in ServiceNow, and notifies logistics when thresholds are breached for Novartis.
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 Novartis."
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://novartis-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://novartis.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
ServiceNow Change Request for SAP Patch
▼
itsm change-management servicenow sap microsoft-teams
Creates a ServiceNow change request for a planned SAP system patch, captures the maintenance window, and notifies affected business units via Microsoft Teams.
naftiko: "0.5"
info:
label: "ServiceNow Change Request for SAP Patch"
description: "Creates a ServiceNow change request for a planned SAP system patch, captures the maintenance window, and notifies affected business units via Microsoft Teams."
tags:
- itsm
- change-management
- servicenow
- sap
- microsoft-teams
capability:
exposes:
- type: mcp
namespace: sap-change-ops
port: 8080
tools:
- name: create-sap-patch-change-request
description: "Given SAP system ID, patch description, and maintenance window, create a ServiceNow change request and notify affected business owners via Microsoft Teams. Use for SAP system patching and maintenance events."
inputParameters:
- name: sap_system_id
in: body
type: string
description: "The SAP system ID being patched (e.g., 'PRD', 'QAS')."
- name: patch_description
in: body
type: string
description: "Description of the SAP patch or maintenance activity."
- name: maintenance_start
in: body
type: string
description: "Planned maintenance window start in ISO 8601 format."
- name: maintenance_end
in: body
type: string
description: "Planned maintenance window end in ISO 8601 format."
- name: teams_channel_id
in: body
type: string
description: "Teams channel ID to notify of the planned maintenance."
steps:
- name: create-change-request
type: call
call: "servicenow.create-change-request"
with:
short_description: "SAP {{sap_system_id}} patch: {{patch_description}}"
category: "Software"
planned_start_date: "{{maintenance_start}}"
planned_end_date: "{{maintenance_end}}"
- name: notify-business-owners
type: call
call: "msteams.post-channel-message"
with:
channel_id: "{{teams_channel_id}}"
text: "SAP Maintenance Notice: {{sap_system_id}} will be patched from {{maintenance_start}} to {{maintenance_end}}. Change Request: {{create-change-request.number}}. Plan accordingly."
consumes:
- type: http
namespace: servicenow
baseUri: "https://novartis.service-now.com/api/now"
authentication:
type: basic
username: "$secrets.servicenow_user"
password: "$secrets.servicenow_password"
resources:
- name: change-requests
path: "/table/change_request"
operations:
- name: create-change-request
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msgraph_token"
resources:
- name: channel-messages
path: "/teams/{{team_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: team_id
in: path
- name: channel_id
in: path
operations:
- name: post-channel-message
method: POST
ServiceNow CMDB Asset Lookup
▼
it-operations servicenow cmdb lookup
Retrieves configuration item details from ServiceNow CMDB by asset tag for Novartis IT asset management.
naftiko: "0.5"
info:
label: "ServiceNow CMDB Asset Lookup"
description: "Retrieves configuration item details from ServiceNow CMDB by asset tag for Novartis 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://novartis.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
ServiceNow IT Asset Retirement
▼
itsm asset-management servicenow okta slack
When an IT asset is marked for retirement in ServiceNow, removes the asset's associated Okta application assignments and posts a completion notice to the IT Slack channel.
naftiko: "0.5"
info:
label: "ServiceNow IT Asset Retirement"
description: "When an IT asset is marked for retirement in ServiceNow, removes the asset's associated Okta application assignments and posts a completion notice to the IT Slack channel."
tags:
- itsm
- asset-management
- servicenow
- okta
- slack
capability:
exposes:
- type: mcp
namespace: asset-retirement
port: 8080
tools:
- name: retire-it-asset
description: "Given a ServiceNow asset configuration item ID and associated Okta application ID, update the asset state to retired, deactivate the Okta application assignment, and notify the IT Slack channel. Use when decommissioning IT hardware or software."
inputParameters:
- name: servicenow_ci_id
in: body
type: string
description: "The ServiceNow configuration item sys_id to retire."
- name: okta_app_id
in: body
type: string
description: "The Okta application ID associated with the retiring asset."
- name: slack_channel
in: body
type: string
description: "IT Slack channel to notify on asset retirement completion."
steps:
- name: update-asset-state
type: call
call: "servicenow.update-ci"
with:
sys_id: "{{servicenow_ci_id}}"
install_status: "7"
- name: deactivate-okta-app
type: call
call: "okta.deactivate-application"
with:
app_id: "{{okta_app_id}}"
- name: notify-it-team
type: call
call: "slack.post-message"
with:
channel: "{{slack_channel}}"
text: "IT Asset Retired: CI {{servicenow_ci_id}} marked retired. Okta application {{okta_app_id}} deactivated."
consumes:
- type: http
namespace: servicenow
baseUri: "https://novartis.service-now.com/api/now"
authentication:
type: basic
username: "$secrets.servicenow_user"
password: "$secrets.servicenow_password"
resources:
- name: configuration-items
path: "/table/cmdb_ci/{{sys_id}}"
inputParameters:
- name: sys_id
in: path
operations:
- name: update-ci
method: PATCH
- type: http
namespace: okta
baseUri: "https://novartis.okta.com/api/v1"
authentication:
type: apikey
key: "Authorization"
value: "$secrets.okta_api_token"
placement: header
resources:
- name: applications
path: "/apps/{{app_id}}/lifecycle/deactivate"
inputParameters:
- name: app_id
in: path
operations:
- name: deactivate-application
method: POST
- type: http
namespace: slack
baseUri: "https://slack.com/api"
authentication:
type: bearer
token: "$secrets.slack_bot_token"
resources:
- name: messages
path: "/chat.postMessage"
operations:
- name: post-message
method: POST
ServiceNow P1 Incident Escalation
▼
itsm servicenow microsoft-teams incident-response
When a ServiceNow P1 incident is unacknowledged past the SLA, escalates to the on-call manager via Microsoft Teams and updates the incident record.
naftiko: "0.5"
info:
label: "ServiceNow P1 Incident Escalation"
description: "When a ServiceNow P1 incident is unacknowledged past the SLA, escalates to the on-call manager via Microsoft Teams and updates the incident record."
tags:
- itsm
- servicenow
- microsoft-teams
- incident-response
capability:
exposes:
- type: mcp
namespace: itsm-ops
port: 8080
tools:
- name: escalate-p1-incident
description: "Given a ServiceNow incident number and on-call manager UPN, update the incident escalation field and notify the manager via Microsoft Teams. Use when a P1 incident breaches its acknowledgment SLA."
inputParameters:
- name: incident_number
in: body
type: string
description: "The ServiceNow incident number (e.g., 'INC0012345')."
- name: manager_upn
in: body
type: string
description: "The UPN (email) of the on-call escalation manager."
steps:
- name: get-incident
type: call
call: "servicenow.get-incident"
with:
number: "{{incident_number}}"
- name: update-escalation
type: call
call: "servicenow-update.update-incident"
with:
sys_id: "{{get-incident.sys_id}}"
escalation: "1"
- name: notify-manager
type: call
call: "msteams.send-message"
with:
recipient_upn: "{{manager_upn}}"
text: "ESCALATED: P1 Incident {{incident_number}} — {{get-incident.short_description}}. Please acknowledge immediately."
consumes:
- type: http
namespace: servicenow
baseUri: "https://novartis.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
- type: http
namespace: servicenow-update
baseUri: "https://novartis.service-now.com/api/now"
authentication:
type: basic
username: "$secrets.servicenow_user"
password: "$secrets.servicenow_password"
resources:
- name: incident-record
path: "/table/incident/{{sys_id}}"
inputParameters:
- name: sys_id
in: path
operations:
- name: update-incident
method: PATCH
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msgraph_token"
resources:
- name: mail
path: "/users/{{recipient_upn}}/sendMail"
inputParameters:
- name: recipient_upn
in: path
operations:
- name: send-message
method: POST
SharePoint SOP Document Retrieval
▼
quality sharepoint document-management sop
Retrieves standard operating procedure document metadata from SharePoint by document name for Novartis quality operations.
naftiko: "0.5"
info:
label: "SharePoint SOP Document Retrieval"
description: "Retrieves standard operating procedure document metadata from SharePoint by document name for Novartis 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://novartis.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
Snowflake Clinical Data Pipeline Monitor
▼
data analytics snowflake slack clinical-data monitoring
Monitors Snowflake for failed or stalled clinical data pipeline jobs and posts an alert to the data engineering Slack channel.
naftiko: "0.5"
info:
label: "Snowflake Clinical Data Pipeline Monitor"
description: "Monitors Snowflake for failed or stalled clinical data pipeline jobs and posts an alert to the data engineering Slack channel."
tags:
- data
- analytics
- snowflake
- slack
- clinical-data
- monitoring
capability:
exposes:
- type: mcp
namespace: clinical-data-ops
port: 8080
tools:
- name: monitor-clinical-pipeline
description: "Query Snowflake for failed pipeline tasks in the clinical data warehouse in the past 24 hours and post alerts to Slack. Use for daily clinical data quality and pipeline monitoring."
inputParameters:
- name: warehouse_name
in: body
type: string
description: "The Snowflake virtual warehouse to monitor (e.g., 'CLINICAL_WH')."
- name: slack_channel
in: body
type: string
description: "Slack channel to post pipeline alerts to (e.g., '#clinical-data-ops')."
steps:
- name: check-failed-tasks
type: call
call: "snowflake.execute-statement"
with:
statement: "SELECT NAME, STATE, ERROR_MESSAGE FROM SNOWFLAKE.ACCOUNT_USAGE.TASK_HISTORY WHERE WAREHOUSE_NAME = '{{warehouse_name}}' AND STATE = 'FAILED' AND SCHEDULED_TIME >= DATEADD(HOUR, -24, CURRENT_TIMESTAMP)"
- name: post-alert
type: call
call: "slack.post-message"
with:
channel: "{{slack_channel}}"
text: "Clinical Data Pipeline Alert: Snowflake warehouse {{warehouse_name}} — failed tasks detected in the last 24 hours. Please investigate immediately."
consumes:
- type: http
namespace: snowflake
baseUri: "https://novartis.snowflakecomputing.com/api/v2"
authentication:
type: bearer
token: "$secrets.snowflake_token"
resources:
- name: statements
path: "/statements"
operations:
- name: execute-statement
method: POST
- type: http
namespace: slack
baseUri: "https://slack.com/api"
authentication:
type: bearer
token: "$secrets.slack_bot_token"
resources:
- name: messages
path: "/chat.postMessage"
operations:
- name: post-message
method: POST
Snowflake Clinical Query Runner
▼
clinical-trials snowflake data-warehouse analytics
Executes a predefined SQL query against the Novartis 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 Novartis 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://novartis.snowflakecomputing.com/api/v2"
authentication:
type: bearer
token: "$secrets.snowflake_token"
resources:
- name: statements
path: "/statements"
operations:
- name: execute-query
method: POST
Snowflake Genomics Data Quality Assertion
▼
data analytics snowflake slack data-quality genomics
Executes a data quality SQL assertion against the Novartis genomics Snowflake table and posts pass/fail results to the data science Slack channel.
naftiko: "0.5"
info:
label: "Snowflake Genomics Data Quality Assertion"
description: "Executes a data quality SQL assertion against the Novartis genomics Snowflake table and posts pass/fail results to the data science Slack channel."
tags:
- data
- analytics
- snowflake
- slack
- data-quality
- genomics
capability:
exposes:
- type: mcp
namespace: genomics-data-quality
port: 8080
tools:
- name: run-genomics-data-check
description: "Execute a data quality assertion against a Snowflake genomics table and post pass/fail results to Slack. Use before loading genomics data into downstream ML pipelines or research databases."
inputParameters:
- name: table_name
in: body
type: string
description: "Snowflake fully-qualified table name (e.g., 'GENOMICS_DB.PUBLIC.VARIANT_CALLS')."
- name: quality_check_sql
in: body
type: string
description: "The SQL assertion to execute. Should return 0 rows on pass."
- name: slack_channel
in: body
type: string
description: "Slack channel to post quality check results to."
steps:
- name: execute-check
type: call
call: "snowflake.execute-statement"
with:
statement: "{{quality_check_sql}}"
- name: post-result
type: call
call: "slack.post-message"
with:
channel: "{{slack_channel}}"
text: "Genomics Data Quality Check on {{table_name}}: Query executed. Review results in Snowflake — statement handle: {{execute-check.statementHandle}}"
consumes:
- type: http
namespace: snowflake
baseUri: "https://novartis.snowflakecomputing.com/api/v2"
authentication:
type: bearer
token: "$secrets.snowflake_token"
resources:
- name: statements
path: "/statements"
operations:
- name: execute-statement
method: POST
- type: http
namespace: slack
baseUri: "https://slack.com/api"
authentication:
type: bearer
token: "$secrets.slack_bot_token"
resources:
- name: messages
path: "/chat.postMessage"
operations:
- name: post-message
method: POST
Supply Chain Shipment Delay Escalation
▼
supply-chain sap servicenow logistics
Detects shipment delays in SAP, creates a ServiceNow case, and alerts the logistics team for Novartis.
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 Novartis."
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://novartis.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
Tableau Dashboard Refresh Trigger
▼
data analytics tableau microsoft-teams
Triggers a Tableau workbook extract refresh for a specified data source and notifies the analytics team via Microsoft Teams when complete.
naftiko: "0.5"
info:
label: "Tableau Dashboard Refresh Trigger"
description: "Triggers a Tableau workbook extract refresh for a specified data source and notifies the analytics team via Microsoft Teams when complete."
tags:
- data
- analytics
- tableau
- microsoft-teams
capability:
exposes:
- type: mcp
namespace: analytics-ops
port: 8080
tools:
- name: refresh-tableau-dashboard
description: "Given a Tableau datasource ID, trigger an extract refresh and notify the analytics team channel via Microsoft Teams. Use before executive meetings or when source data has been updated."
inputParameters:
- name: datasource_id
in: body
type: string
description: "The Tableau datasource ID to refresh (GUID format)."
- name: teams_channel_id
in: body
type: string
description: "Microsoft Teams channel ID to notify on completion."
steps:
- name: trigger-refresh
type: call
call: "tableau.refresh-datasource"
with:
datasource_id: "{{datasource_id}}"
- name: notify-analytics
type: call
call: "msteams.post-channel-message"
with:
channel_id: "{{teams_channel_id}}"
text: "Tableau datasource refresh triggered for {{datasource_id}}. Job ID: {{trigger-refresh.job_id}}. Dashboard will be updated shortly."
consumes:
- type: http
namespace: tableau
baseUri: "https://10ax.online.tableau.com/api/2.8"
authentication:
type: apikey
key: "X-Tableau-Auth"
value: "$secrets.tableau_token"
placement: header
resources:
- name: datasource-refreshes
path: "/sites/{{site_id}}/datasources/{{datasource_id}}/refresh"
inputParameters:
- name: site_id
in: path
- name: datasource_id
in: path
operations:
- name: refresh-datasource
method: POST
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msgraph_token"
resources:
- name: channel-messages
path: "/teams/{{team_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: team_id
in: path
- name: channel_id
in: path
operations:
- name: post-channel-message
method: POST
Tableau Workbook Access Audit
▼
data analytics tableau confluence audit governance
Queries Tableau Server for all workbooks accessible to a specified user group and publishes a data access audit report to Confluence for governance review.
naftiko: "0.5"
info:
label: "Tableau Workbook Access Audit"
description: "Queries Tableau Server for all workbooks accessible to a specified user group and publishes a data access audit report to Confluence for governance review."
tags:
- data
- analytics
- tableau
- confluence
- audit
- governance
capability:
exposes:
- type: mcp
namespace: data-governance
port: 8080
tools:
- name: audit-tableau-access
description: "Fetch all Tableau workbooks and data sources accessible to a specified user group and publish a data access audit to Confluence. Use for data governance reviews or GDPR access compliance checks."
inputParameters:
- name: group_id
in: body
type: string
description: "The Tableau user group ID to audit access for."
- name: confluence_space_key
in: body
type: string
description: "Confluence space key for the access audit report."
- name: confluence_parent_id
in: body
type: string
description: "Confluence parent page ID for the audit report."
steps:
- name: get-group-workbooks
type: call
call: "tableau.list-group-workbooks"
with:
group_id: "{{group_id}}"
- name: publish-audit
type: call
call: "confluence.create-page"
with:
space_key: "{{confluence_space_key}}"
parent_page_id: "{{confluence_parent_id}}"
title: "Tableau Data Access Audit — Group {{group_id}}"
content: "Tableau workbook and datasource access audit for group {{group_id}}. Total accessible assets: {{get-group-workbooks.pagination.totalAvailable}}."
consumes:
- type: http
namespace: tableau
baseUri: "https://10ax.online.tableau.com/api/2.8"
authentication:
type: apikey
key: "X-Tableau-Auth"
value: "$secrets.tableau_token"
placement: header
resources:
- name: group-workbooks
path: "/sites/{{site_id}}/groups/{{group_id}}/workbooks"
inputParameters:
- name: site_id
in: path
- name: group_id
in: path
operations:
- name: list-group-workbooks
method: GET
- type: http
namespace: confluence
baseUri: "https://novartis.atlassian.net/wiki/rest/api"
authentication:
type: basic
username: "$secrets.confluence_user"
password: "$secrets.confluence_api_token"
resources:
- name: pages
path: "/content"
operations:
- name: create-page
method: POST
Tableau Workbook Refresh Status
▼
analytics tableau reporting lookup
Checks the last extract refresh status for a Tableau workbook for Novartis analytics operations.
naftiko: "0.5"
info:
label: "Tableau Workbook Refresh Status"
description: "Checks the last extract refresh status for a Tableau workbook for Novartis 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://novartis.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
Terraform Infrastructure Provisioning with Approval
▼
devops terraform servicenow cloud
Manages infrastructure provisioning by creating ServiceNow change requests, triggering Terraform plans, and notifying the cloud team for Novartis.
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 Novartis."
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://novartis.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
Veeva Vault Audit Trail Report
▼
regulatory veeva confluence audit compliance
Extracts a Veeva Vault audit trail for a specified document and publishes the report to Confluence for regulatory inspection readiness.
naftiko: "0.5"
info:
label: "Veeva Vault Audit Trail Report"
description: "Extracts a Veeva Vault audit trail for a specified document and publishes the report to Confluence for regulatory inspection readiness."
tags:
- regulatory
- veeva
- confluence
- audit
- compliance
capability:
exposes:
- type: mcp
namespace: vault-audit
port: 8080
tools:
- name: generate-vault-audit-trail
description: "Given a Veeva Vault document ID, extract the full audit trail and publish it to Confluence under the inspection readiness space. Use to prepare for regulatory inspections or internal audits."
inputParameters:
- name: vault_document_id
in: body
type: string
description: "The Veeva Vault document ID for audit trail extraction."
- name: confluence_space_key
in: body
type: string
description: "Confluence space key for the audit trail report."
- name: confluence_parent_id
in: body
type: string
description: "Confluence parent page ID for the audit report."
steps:
- name: get-audit-trail
type: call
call: "veeva.get-document-audit-trail"
with:
document_id: "{{vault_document_id}}"
- name: publish-audit-report
type: call
call: "confluence.create-page"
with:
space_key: "{{confluence_space_key}}"
parent_page_id: "{{confluence_parent_id}}"
title: "Vault Audit Trail — Document {{vault_document_id}}"
content: "Veeva Vault document audit trail for document ID {{vault_document_id}}. Generated for inspection readiness. Total events: {{get-audit-trail.responseDetails.total}}."
consumes:
- type: http
namespace: veeva
baseUri: "https://novartis.veevavault.com/api/v24.1"
authentication:
type: bearer
token: "$secrets.veeva_token"
resources:
- name: document-audit-trail
path: "/objects/documents/{{document_id}}/audit_trail"
inputParameters:
- name: document_id
in: path
operations:
- name: get-document-audit-trail
method: GET
- type: http
namespace: confluence
baseUri: "https://novartis.atlassian.net/wiki/rest/api"
authentication:
type: basic
username: "$secrets.confluence_user"
password: "$secrets.confluence_api_token"
resources:
- name: pages
path: "/content"
operations:
- name: create-page
method: POST
Veeva Vault Document Approval Status Check
▼
regulatory veeva document-management
Retrieves the current workflow status and reviewer list for a regulatory document in Veeva Vault.
naftiko: "0.5"
info:
label: "Veeva Vault Document Approval Status Check"
description: "Retrieves the current workflow status and reviewer list for a regulatory document in Veeva Vault."
tags:
- regulatory
- veeva
- document-management
capability:
exposes:
- type: mcp
namespace: regulatory-reporting
port: 8080
tools:
- name: get-document-approval-status
description: "Given a Veeva Vault document ID, return the current lifecycle state, workflow status, and list of pending reviewers. Use to check regulatory document approval progress before submission deadlines."
inputParameters:
- name: document_id
in: body
type: string
description: "The Veeva Vault document ID to check (numeric)."
call: "veeva.get-document"
with:
document_id: "{{document_id}}"
outputParameters:
- name: lifecycle_state
type: string
mapping: "$.document.lifecycle_state__v"
- name: status
type: string
mapping: "$.document.status__v"
- name: modified_date
type: string
mapping: "$.document.version_modified_date__v"
consumes:
- type: http
namespace: veeva
baseUri: "https://novartis.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
Veeva Vault Document Status Lookup
▼
regulatory veeva-vault document-management lookup
Retrieves the current lifecycle status of a document in Veeva Vault by document ID for Novartis 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 Novartis 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://novartis.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
Veeva Vault to SAP Contract Sync
▼
procurement veeva sap contract-management
When a vendor contract is approved in Veeva Vault, extracts key terms and creates the corresponding SAP contract record for procurement management.
naftiko: "0.5"
info:
label: "Veeva Vault to SAP Contract Sync"
description: "When a vendor contract is approved in Veeva Vault, extracts key terms and creates the corresponding SAP contract record for procurement management."
tags:
- procurement
- veeva
- sap
- contract-management
capability:
exposes:
- type: mcp
namespace: contract-sync
port: 8080
tools:
- name: sync-contract-to-sap"
description: "Given a Veeva Vault contract document ID, fetch contract metadata (vendor, value, start/end dates) and create the corresponding vendor contract outline agreement in SAP. Use when a signed contract is approved in Veeva Vault."
inputParameters:
- name: vault_document_id
in: body
type: string
description: "The Veeva Vault document ID of the approved contract."
- name: sap_company_code
in: body
type: string
description: "The SAP company code for the contract (e.g., '1000')."
steps:
- name: get-contract-metadata
type: call
call: "veeva.get-document"
with:
document_id: "{{vault_document_id}}"
- name: create-sap-contract
type: call
call: "sap.create-outline-agreement"
with:
company_code: "{{sap_company_code}}"
vendor: "{{get-contract-metadata.vendor_number__c}}"
start_date: "{{get-contract-metadata.contract_start_date__c}}"
end_date: "{{get-contract-metadata.contract_end_date__c}}"
consumes:
- type: http
namespace: veeva
baseUri: "https://novartis.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
- type: http
namespace: sap
baseUri: "https://novartis-s4.sap.com/sap/opu/odata/sap/MM_PUR_CONTRACT_MAINTAIN_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: outline-agreements
path: "/A_OutlineAgreement"
operations:
- name: create-outline-agreement
method: POST
Vendor Qualification Review Orchestrator
▼
procurement sap servicenow vendor-management
Orchestrates vendor qualification reviews by pulling vendor data from SAP, creating a ServiceNow assessment task, and notifying procurement for Novartis.
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 Novartis."
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://novartis-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://novartis.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
Workday Absence Balance Lookup
▼
hr workday absence lookup
Retrieves employee absence and leave balance from Workday for Novartis HR operations.
naftiko: "0.5"
info:
label: "Workday Absence Balance Lookup"
description: "Retrieves employee absence and leave balance from Workday for Novartis 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/novartis/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
Workday Absence Management Alert
▼
hr absence-management workday microsoft-teams compliance
Monitors Workday for employees with unexpected absence patterns exceeding policy thresholds and notifies their managers via Microsoft Teams.
naftiko: "0.5"
info:
label: "Workday Absence Management Alert"
description: "Monitors Workday for employees with unexpected absence patterns exceeding policy thresholds and notifies their managers via Microsoft Teams."
tags:
- hr
- absence-management
- workday
- microsoft-teams
- compliance
capability:
exposes:
- type: mcp
namespace: absence-monitoring
port: 8080
tools:
- name: alert-absence-threshold
description: "Check Workday for employees whose unplanned absence days exceed the policy threshold in the current quarter and notify their managers via Microsoft Teams. Use for HR compliance monitoring."
inputParameters:
- name: absence_threshold_days
in: body
type: integer
description: "Number of unplanned absence days that triggers an alert."
- name: period
in: body
type: string
description: "The monitoring period (e.g., 'Q1-2026')."
steps:
- name: get-absence-data
type: call
call: "workday.get-absence-entries"
with:
period: "{{period}}"
type: "unplanned"
- name: notify-hr
type: call
call: "msteams.post-channel-message"
with:
channel_id: "HR_GENERAL_CHANNEL_ID"
text: "Absence Alert: Employees exceeding {{absence_threshold_days}} unplanned absence days in {{period}} have been identified. Please review in Workday."
consumes:
- type: http
namespace: workday
baseUri: "https://wd2-impl-services1.workday.com/ccx/api/v1"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: absence-entries
path: "/novartis/absenceEntries"
inputParameters:
- name: period
in: query
- name: type
in: query
operations:
- name: get-absence-entries
method: GET
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msgraph_token"
resources:
- name: channel-messages
path: "/teams/{{team_id}}/channels/{{channel_id}}/messages"
inputParameters:
- name: team_id
in: path
- name: channel_id
in: path
operations:
- name: post-channel-message
method: POST
Workday Compensation Lookup
▼
hr workday compensation lookup
Retrieves compensation plan details for an employee from Workday for Novartis HR total rewards operations.
naftiko: "0.5"
info:
label: "Workday Compensation Lookup"
description: "Retrieves compensation plan details for an employee from Workday for Novartis 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/novartis/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
Workday Employee Profile Lookup
▼
hr workday employee lookup
Retrieves employee profile details from Workday by employee ID for Novartis HR operations.
naftiko: "0.5"
info:
label: "Workday Employee Profile Lookup"
description: "Retrieves employee profile details from Workday by employee ID for Novartis 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/novartis/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
Workday Learning Completion Compliance Report
▼
hr compliance workday confluence training
Queries Workday Learning for employees who have not completed mandatory compliance training and posts the non-completion report to Confluence.
naftiko: "0.5"
info:
label: "Workday Learning Completion Compliance Report"
description: "Queries Workday Learning for employees who have not completed mandatory compliance training and posts the non-completion report to Confluence."
tags:
- hr
- compliance
- workday
- confluence
- training
capability:
exposes:
- type: mcp
namespace: learning-compliance
port: 8080
tools:
- name: report-training-non-completion
description: "Fetch employees who have not completed mandatory compliance training courses from Workday Learning and publish the list to Confluence. Use for quarterly compliance reporting or audit preparation."
inputParameters:
- name: course_id
in: body
type: string
description: "The Workday Learning course ID for the mandatory training."
- name: deadline
in: body
type: string
description: "Training completion deadline in ISO 8601 format."
- name: confluence_space_key
in: body
type: string
description: "Confluence space key for the compliance report."
- name: confluence_parent_id
in: body
type: string
description: "Confluence parent page ID for the report."
steps:
- name: get-non-completions
type: call
call: "workday.get-learning-non-completions"
with:
course_id: "{{course_id}}"
deadline: "{{deadline}}"
- name: publish-report
type: call
call: "confluence.create-page"
with:
space_key: "{{confluence_space_key}}"
parent_page_id: "{{confluence_parent_id}}"
title: "Mandatory Training Non-Completion Report — Course {{course_id}}"
content: "Employees who have not completed mandatory training course {{course_id}} by {{deadline}}. Total non-completions: {{get-non-completions.total}}."
consumes:
- type: http
namespace: workday
baseUri: "https://wd2-impl-services1.workday.com/ccx/api/learning/v1"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: learning-records
path: "/novartis/learningRecords"
inputParameters:
- name: course_id
in: query
- name: deadline
in: query
operations:
- name: get-learning-non-completions
method: GET
- type: http
namespace: confluence
baseUri: "https://novartis.atlassian.net/wiki/rest/api"
authentication:
type: basic
username: "$secrets.confluence_user"
password: "$secrets.confluence_api_token"
resources:
- name: pages
path: "/content"
operations:
- name: create-page
method: POST
Workday Learning Compliance Reminder
▼
hr workday compliance training
Identifies overdue compliance training assignments in Workday and sends reminder notifications for Novartis.
naftiko: "0.5"
info:
label: "Workday Learning Compliance Reminder"
description: "Identifies overdue compliance training assignments in Workday and sends reminder notifications for Novartis."
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/novartis/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
Workday Payroll Period Close Verification
▼
finance payroll workday sap period-close
Verifies that all payroll journal entries have been posted and reconciled in SAP before the monthly close, posting a confirmation to the finance Slack channel.
naftiko: "0.5"
info:
label: "Workday Payroll Period Close Verification"
description: "Verifies that all payroll journal entries have been posted and reconciled in SAP before the monthly close, posting a confirmation to the finance Slack channel."
tags:
- finance
- payroll
- workday
- sap
- period-close
capability:
exposes:
- type: mcp
namespace: payroll-close
port: 8080
tools:
- name: verify-payroll-period-close
description: "Fetch payroll journal status from Workday and verify reconciliation in SAP for a given pay period. Post the close verification status to the finance Slack channel. Use at month-end payroll close."
inputParameters:
- name: pay_period
in: body
type: string
description: "The payroll period identifier (e.g., '2026-03')."
- name: company_code
in: body
type: string
description: "The SAP company code for the legal entity (e.g., '1000')."
- name: slack_channel
in: body
type: string
description: "Slack channel for the close verification status."
steps:
- name: get-payroll-journals
type: call
call: "workday.get-payroll-journals"
with:
pay_period: "{{pay_period}}"
- name: verify-sap-posting
type: call
call: "sap.get-gl-documents"
with:
company_code: "{{company_code}}"
posting_period: "{{pay_period}}"
document_type: "PC"
- name: post-status
type: call
call: "slack.post-message"
with:
channel: "{{slack_channel}}"
text: "Payroll Period Close {{pay_period}}: Workday journals — {{get-payroll-journals.status}}. SAP posting — {{verify-sap-posting.count}} documents found."
consumes:
- type: http
namespace: workday
baseUri: "https://wd2-impl-services1.workday.com/ccx/api/v1"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: payroll-journals
path: "/novartis/payrollResults"
inputParameters:
- name: pay_period
in: query
operations:
- name: get-payroll-journals
method: GET
- type: http
namespace: sap
baseUri: "https://novartis-s4.sap.com/sap/opu/odata/sap/API_JOURNALENTRYITEMBASIC_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: journal-entries
path: "/A_JournalEntryItem"
inputParameters:
- name: company_code
in: query
- name: posting_period
in: query
- name: document_type
in: query
operations:
- name: get-gl-documents
method: GET
outputRawFormat: xml
- type: http
namespace: slack
baseUri: "https://slack.com/api"
authentication:
type: bearer
token: "$secrets.slack_bot_token"
resources:
- name: messages
path: "/chat.postMessage"
operations:
- name: post-message
method: POST
Workday Position Requisition Approval Workflow
▼
hr workday sap hiring
Processes new position requisitions by validating budget in SAP, creating the requisition in Workday, and notifying HR for Novartis.
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 Novartis."
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://novartis-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/novartis/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
Workday Recruiting Offer Letter Workflow
▼
hr recruiting workday microsoft-teams approval
When a candidate is moved to Offer stage in Workday Recruiting, generates an offer summary and routes it to the hiring manager via Microsoft Teams for final approval.
naftiko: "0.5"
info:
label: "Workday Recruiting Offer Letter Workflow"
description: "When a candidate is moved to Offer stage in Workday Recruiting, generates an offer summary and routes it to the hiring manager via Microsoft Teams for final approval."
tags:
- hr
- recruiting
- workday
- microsoft-teams
- approval
capability:
exposes:
- type: mcp
namespace: offer-management
port: 8080
tools:
- name: route-offer-approval
description: "Given a Workday candidate ID and hiring manager UPN, fetch candidate and role details from Workday and send an offer approval request to the hiring manager via Microsoft Teams. Use when a candidate reaches the offer stage."
inputParameters:
- name: candidate_id
in: body
type: string
description: "The Workday candidate ID in the offer stage."
- name: requisition_id
in: body
type: string
description: "The Workday job requisition ID for the role."
- name: hiring_manager_upn
in: body
type: string
description: "The UPN (email) of the hiring manager for approval."
steps:
- name: get-candidate
type: call
call: "workday.get-candidate"
with:
candidate_id: "{{candidate_id}}"
- name: get-requisition
type: call
call: "workday-req.get-requisition"
with:
req_id: "{{requisition_id}}"
- name: notify-hiring-manager
type: call
call: "msteams.send-message"
with:
recipient_upn: "{{hiring_manager_upn}}"
text: "Offer Approval Required: Candidate {{get-candidate.full_name}} for role {{get-requisition.jobRequisitionTitle}}. Please review and approve the offer in Workday."
consumes:
- type: http
namespace: workday
baseUri: "https://wd2-impl-services1.workday.com/ccx/api/recruiting/v1"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: candidates
path: "/candidates/{{candidate_id}}"
inputParameters:
- name: candidate_id
in: path
operations:
- name: get-candidate
method: GET
- type: http
namespace: workday-req
baseUri: "https://wd2-impl-services1.workday.com/ccx/api/recruiting/v1"
authentication:
type: bearer
token: "$secrets.workday_token"
resources:
- name: requisitions
path: "/jobRequisitions/{{req_id}}"
inputParameters:
- name: req_id
in: path
operations:
- name: get-requisition
method: GET
- type: http
namespace: msteams
baseUri: "https://graph.microsoft.com/v1.0"
authentication:
type: bearer
token: "$secrets.msgraph_token"
resources:
- name: mail
path: "/users/{{recipient_upn}}/sendMail"
inputParameters:
- name: recipient_upn
in: path
operations:
- name: send-message
method: POST
Workday Role Change and SAP Cost Center Update
▼
hr finance workday sap cost-center
When an employee's organizational unit changes in Workday, updates the corresponding cost center assignment in SAP to ensure correct financial allocation.
naftiko: "0.5"
info:
label: "Workday Role Change and SAP Cost Center Update"
description: "When an employee's organizational unit changes in Workday, updates the corresponding cost center assignment in SAP to ensure correct financial allocation."
tags:
- hr
- finance
- workday
- sap
- cost-center
capability:
exposes:
- type: mcp
namespace: org-finance-sync
port: 8080
tools:
- name: sync-cost-center-change
description: "Given a Workday employee ID and new cost center, update the employee's cost center assignment in SAP to reflect the organizational change. Use when an employee transfers departments or business units."
inputParameters:
- name: workday_employee_id
in: body
type: string
description: "The Workday worker ID of the transferring employee."
- name: new_cost_center
in: body
type: string
description: "The new SAP cost center code (e.g., 'CC-1042')."
- name: effective_date
in: body
type: string
description: "Date the cost center change is effective in ISO 8601 format."
steps:
- name: get-employee
type: call
call: "workday.get-worker"
with:
worker_id: "{{workday_employee_id}}"
- name: update-sap-cost-center
type: call
call: "sap.update-employee-cost-center"
with:
personnel_number: "{{get-employee.sap_personnel_number}}"
cost_center: "{{new_cost_center}}"
start_date: "{{effective_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: "/novartis/workers/{{worker_id}}"
inputParameters:
- name: worker_id
in: path
operations:
- name: get-worker
method: GET
- type: http
namespace: sap
baseUri: "https://novartis-s4.sap.com/sap/opu/odata/sap/API_COSTCENTERASSIGNMENT_SRV"
authentication:
type: basic
username: "$secrets.sap_user"
password: "$secrets.sap_password"
resources:
- name: cost-center-assignments
path: "/A_CostCenterAssignment"
operations:
- name: update-employee-cost-center
method: POST