SAP Integration Suite
Category: EHR & Practice Mgmt
Node id: sap-integration-suite
Standards: SOC2
Integrates with SAP Integration Suite (CPI/BTP) for message routing, iFlow execution, and message log retrieval
What it does
- SAP CPI/BTP iFlow message sending
- Message processing log retrieval
- iFlow deployment status monitoring
- OAuth2 client credentials authentication
- Custom header and content type support
Use cases
- Send messages to SAP Integration Suite iFlows
- Monitor integration flow execution status and logs
- Orchestrate SAP middleware in healthcare data pipelines
Runtime
- Performance tier:
variable
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
payload | json | No | JSON payload for send_message operation |
raw_payload | text | No | Raw text payload for send_message operation (e.g. XML, HL7) |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
response | json | No | Response from iFlow execution |
http_status | number | No | HTTP status code |
message_id | text | No | SAP message processing log ID |
content_type | text | No | Response content type |
logs | json | No | Message processing logs (get_message_logs) |
iflow_status | json | No | iFlow runtime artifact status (get_iflow_status) |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| iFlow URL | iflow_url | string | Yes | URL of the SAP CPI iFlow endpoint | ||
| Operation | operation | enum | No | send_message | send_message, get_message_logs, get_iflow_status | Integration Suite operation to perform |
Auth
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Auth Token | auth_token | secret | No | Bearer token for authentication (alternative to OAuth2) | ||
| Client ID | client_id | string | No | OAuth2 client ID for token fetch | ||
| Client Secret | client_secret | secret | No | OAuth2 client secret for token fetch | ||
| Token URL | token_url | string | No | OAuth2 token endpoint URL |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Content Type | content_type | string | No | application/json | Content-Type header for send_message | |
| Custom Headers | custom_headers | json | No | Additional HTTP headers as key-value pairs | ||
| Log Limit | top | number | No | 50 | min 1; max 1000 | Maximum number of message logs to retrieve |
Errors
| Code | Description |
|---|---|
IFLOW_URL_REQUIRED | iFlow endpoint URL must be configured |
AUTH_FAILED | Authentication to SAP CPI failed |
SEND_FAILED | Failed to send message to iFlow |
UNSUPPORTED_OPERATION | Operation not recognized |
Runtime notes
- send_message outputs response, http_status, message_id, and content_type; logs and iflow_status are nil
- OAuth2 token is auto-fetched when client_id, client_secret, and token_url are all set
- If the iFlow returns non-JSON, the raw text is placed in response.raw_response
- message_id is extracted from the SAP_MessageProcessingLogID response header
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Quelque chose n'est pas clair ? Envoyez vos commentaires sur la documentation par courriel.