iGlow / Create an iFlow with AI

Guide · Create

Create an SAP CPI iFlow with AI

Updated 31 October 2026 · by the iGlow team at StellarClouds

Steps

1. Install iGlow from the Chrome Web Store (it also works in Microsoft Edge) and sign in with Google.
2. Open your tenant in Integration Suite and click the iGlow icon. The side panel opens next to it. Tag the tenant DEV, QA or PRD.
3. Describe the flow. Say how it starts (for example HTTPS, Timer or SFTP), which systems it calls, and what happens in between. Example: Create an iFlow PinCode_Lookup: HTTPS POST with {"pincode"}, call api.postalpincode.in, return the post offices as JSON. For bigger work, attach the specification file; iGlow reads the sections it needs.
4. Review the plan. iGlow lists the steps and routes and shows any Groovy script before anything is created. Ask for changes or click Create.
5. Let it test. iGlow runs SAP's simulation over the new steps and routes, with mocked receivers so no external system is called.
6. Deploy when ready. Deploy waits for your click. Afterwards, send a test call from the Test tab.

What it can build

• Sender and receiver adapters such as HTTPS, HTTP, SOAP, SFTP, JMS and Mail, at the versions your tenant supports
• Content Modifiers, Routers with conditions, request-reply calls and JSON to XML converters
• Groovy scripts and XSLT, checked for common runtime mistakes when they are saved
• Message mappings, including mappings created from XSD files and standard mapping functions
• Exception subprocesses, Error End Events, Local Integration Processes and Process Calls
• Externalized parameters: write {{Host}} in a step and it becomes a configurable parameter

New iFlows follow SAP's integration design guidelines, and iGlow runs the same Problems check as SAP's editor.

Changing an existing iFlow

The same chat changes iFlows you already have: add a step after another one, add a route, externalize hard-coded values, or connect and disconnect steps. Every change is shown before it is saved, and iGlow takes a snapshot first, so Undo restores the previous version.

Limits

• On a tenant tagged PRD, iGlow never creates, changes or deploys anything.
• Custom functions in message mappings can be read, with their Groovy source, but not written yet.
• Credentials, certificates and Cloud Connector setup stay with you; iGlow tells you what is missing.

Questions

More guides

• AI tools for SAP Integration SuiteWhat exists in 2026 and what each is for
• Fix failed messages in SAP CPIRoot cause, reviewed patch, one-click undo
• Test an iFlow with simulationSimulate changes, then send real test calls
• Trace a CPI message step by stepEach step, its time, and where it failed
• Monitor Timer iFlows and JMS queuesMissed Timer runs, waiting messages, failure hot spots
• ChangelogWhat changed in each release