If this iFlow ID already exists in CPI, it must be closed in the web IDE before Generate can overwrite it.
Thinking...
Design Brief
Generated iFlow
Unlock before any action
All iFlows must be closed in the SAP CPI web IDE before Modify, Fix or Verify can write to them.
Select a package
Choose a package above to see its iFlows
Groovy Generator
Generating...
Generated Script
Checking your tenant connection...
START WITH MONITORING
Know which SAP integrations need attention
Watch critical flows, review failures and runtime trends, and receive email alerts. Connect a tenant to see your own integrations here.
Sample data · No SAP tenant connected
These fictional examples show what you can investigate with monitoring. No live checks or emails are running in this sample.
Example failure
Order_Sync
HTTP 401: receiver rejected the request.
Review the error and check receiver credentials.
Example missed run
Invoice_Export
No run found in the expected time window.
Configure an expected schedule for the flows you want to track.
Connect a test tenant
Choose a few critical flows
Review alerts and press Start
Need access? Ask your SAP administrator for approved API credentials for a test tenant. You can return to this page when access is ready.
Monitoring is off
Watch your critical flows — failures, root causes and runtime trends in one place.
Ask your monitoring
No flows watched yet
Choose a few critical flows, save your watch list, then review alert settings and press Start.
Manage queues
Pick the JMS queues to monitor
Queues used by a flow you already watch are marked suggested. Only selected queues appear on the dashboard and in answers.
Loading…
Manage Watch List
Click a flow to watch it. Watched flows can alert instantly on failure.
Alerts will be sent to:
Loading iFlows from CPI...
Scheduled flow
For flows that run on a timer. We only check inside the window, and alert if an expected run is missed — no wasted checks, no false "no traffic" noise.
Activity
No failures in current session.
Queue actions
These change your tenant. Each needs the matching write scope on your service key. Check Why? first — retrying a poison message won't help.
Move messages to
Message QueuesJMS queue depth, stuck messages, and retry backlog
Queue Health
Loading queues…
STEP 1 OF 3 · CONNECT YOUR TENANT
Start with a test tenant
Enter the CPI connection details below and save. Use credentials approved by your SAP administrator. Next, choose the flows you want to watch and review your email settings.
Saving credentials does not start monitoring. Loading your flows will check whether the saved credentials can access the required SAP APIs.
CPI Connection
SAP Integration Suite tenant credentials
BTP Cockpit → Instances & Subscriptions → Integration Suite → Service Key → url
Same Service Key → tokenurl (append /oauth/token if missing)
Service Key → clientid
Service Key → clientsecret
The base URL you see when the web IDE is open — everything before /shell. Lets CPI Copilot link flows straight to the editor.
CPI Runtime
Only needed for Fix/Verify flows — leave blank to share credentials with CPI Connection
Runtime Service Key (plan: integration-flow) → clientid
Runtime Service Key → clientsecret
Runtime Service Key → tokenurl
Runtime Service Key → url (the runtime host, not the design-time host)
Email Alerts
Delivery method for monitor failure notifications
AI Engine
Which AI powers Generate, Explain, Fix and Chat
Stored encrypted per user, never shown again after save
Azure AI Foundry resource endpoint (OpenAI-compatible /openai/v1 path)
Pick a model — or choose Custom to type one
Credentials are encrypted at rest. Your secrets are stored using AES-256-GCM encryption
with a per-account master key. They are never echoed back to the browser and never stored in plain text.
Users (active)
—
AI Spend This Month
—
AI Spend Total
—
CPI Connected
—
Users
Loading...
Recent AI Activity
Loading...
AI AssistantOnline
Ask me anything about SAP CPI — iFlow design, Groovy scripting, troubleshooting, or best practices.