After building my first iFlow in SAP BTP Integration Suite, I was excited to test it — but I wasn’t sure where to start. That’s when I discovered Postman, a simple tool for testing HTTP requests. In this blog, I’ll walk you through how I used Postman to test my iFlow, and what I learned along the way.
🔄What I Built
I created a Mail Adapter iFlow:
Trigger: HTTP POST request Step: Content Modifier (formatting) Output: Mail Adapter (send a notification email)
The goal? Trigger the iFlow from Postman and see the email arrive.
🔧Step 1: Set Up the iFlow
Navigate to Design Workspace
Go to Integration Suite → Design → Integration & APIs
Create a New Package
Click Create PackageEnter Name: Mail_Testing
Add an Artifact to the Package
Open the Mail_Testing packageClick Create → Integration Flow
Configure the iFlow
Name: Mail_SimpleClick Add and Open in Editor
Design and Deploy the Mail iFlow:
Edit the iFlow
Click Edit in the iFlow editor
Modify the Start Event
Delete the default SenderAdd a Timer from the Event sectionDelete the Start element
Configure the Timer
Open the Timer SchedulerKeep the configuration basic (default settings)
Add a Content Modifier
Drag and drop a Content Modifier into the flowConfigure Message Body:Type: ConstantValue:Hi All,
This is for sample testing mail.
Thanks & Regards,
Connect to Mail Receiver
Connect the End of the flow to a ReceiverSelect Mail Adapter as the receiver type
Configure Mail Adapter Connection
Address: smtp.gmail.com:587Protection: OptionalAuthentication: OAuth2 Authorization CodeCredential Name: IS_GMAIL
Set Mail Processing Details
From: Sender’s mailTo: Receiver’s mailSubject: Testing
Save and Deploy
Click SaveClick Deploy to activate the iFlow
Step 2: Configure OAuth2 Authorization Code in SAP BTP Integration Suite
Navigate to Security Material
Go to Integration Suite → Monitor → Integration & APIs → Security Material
Create New OAuth2 Authorization Code
Click CreateSelect OAuth2 Authorization Code as the type.
Fill in Configuration Details
Name: IS_GMAILDescription: Gmail configurationProvider: GenericAuthorization URL: <authuri>?access_type=offline&prompt=consentToken URL: <authuri>/tokenClient ID: <clientid>Client Secret: <clientsecret>Send As: Basic Authentication HeaderUsername: “sender’s mail id”Scope: https://mail.google.com/
🔗Step 3: Get the Endpoint URL
After deployment:
Go to Monitor → Manage Integration Content
Under Monitor- Integrations and API, added a security material for OAuth Authorization.Find your iFlow and copy the endpoint URL
🧪 Step 4: Test in Postman
In Postman:
Method: POST URL: Paste your endpoint Authorization: Basic Auth Use your Integration Suite credentials Headers: Content-Type: application/json Body (raw, JSON):
json
{
“name”: “Pranjali”,
“email”: “abc@example.com“,
“message”: “Test from Postman!”
}
Click Send.
📈Step 5: Check the Results
In SAP BTP:
Go to Monitor → Monitor Message Processing Look for your iFlow execution Open the message to see: Payload trace Adapter logs Success or error details
🧠 Tips & Common Errors that you phase while deploying the iflow:
Error
Cause
Fix
401
Unauthorized Wrong credentials or missing role
Ensure ESBMessaging.send role is assigned
404
Not Found Incorrect endpoint
Verify path /triggerEmail matches exactly
Empty or broken payload
Incorrect headers
Add Content-Type: application/json
Mail not received
Mail adapter config issue
Double-check SMTP host, port, and credentials
Flow doesn’t appear in monitor
Wrong trigger format
Ensure JSON body is well-formed and matches iFlow expectations
✅Final Thoughts
Testing your iFlows doesn’t need to be hard. Postman made it quick and easy for me to validate my flow and debug it. If you’re just getting started with SAP BTP Integration Suite, I highly recommend trying this out with a simple HTTP-to-Mail flow.
After building my first iFlow in SAP BTP Integration Suite, I was excited to test it — but I wasn’t sure where to start. That’s when I discovered Postman, a simple tool for testing HTTP requests. In this blog, I’ll walk you through how I used Postman to test my iFlow, and what I learned along the way. 🔄What I Built I created a Mail Adapter iFlow: Trigger: HTTP POST request Step: Content Modifier (formatting) Output: Mail Adapter (send a notification email) The goal? Trigger the iFlow from Postman and see the email arrive. 🔧Step 1: Set Up the iFlow Navigate to Design WorkspaceGo to Integration Suite → Design → Integration & APIsCreate a New PackageClick Create PackageEnter Name: Mail_TestingAdd an Artifact to the PackageOpen the Mail_Testing packageClick Create → Integration FlowConfigure the iFlowName: Mail_SimpleClick Add and Open in EditorDesign and Deploy the Mail iFlow:Edit the iFlowClick Edit in the iFlow editorModify the Start EventDelete the default SenderAdd a Timer from the Event sectionDelete the Start elementConfigure the TimerOpen the Timer SchedulerKeep the configuration basic (default settings)Add a Content ModifierDrag and drop a Content Modifier into the flowConfigure Message Body:Type: ConstantValue:Hi All,
This is for sample testing mail.
Thanks & Regards,Connect to Mail ReceiverConnect the End of the flow to a ReceiverSelect Mail Adapter as the receiver typeConfigure Mail Adapter ConnectionAddress: smtp.gmail.com:587Protection: OptionalAuthentication: OAuth2 Authorization CodeCredential Name: IS_GMAILSet Mail Processing DetailsFrom: Sender’s mailTo: Receiver’s mailSubject: TestingSave and DeployClick SaveClick Deploy to activate the iFlowStep 2: Configure OAuth2 Authorization Code in SAP BTP Integration SuiteNavigate to Security MaterialGo to Integration Suite → Monitor → Integration & APIs → Security MaterialCreate New OAuth2 Authorization CodeClick CreateSelect OAuth2 Authorization Code as the type.Fill in Configuration DetailsName: IS_GMAILDescription: Gmail configurationProvider: GenericAuthorization URL: <authuri>?access_type=offline&prompt=consentToken URL: <authuri>/tokenClient ID: <clientid>Client Secret: <clientsecret>Send As: Basic Authentication HeaderUsername: “sender’s mail id”Scope: https://mail.google.com/ 🔗Step 3: Get the Endpoint URL After deployment: Go to Monitor → Manage Integration Content Under Monitor- Integrations and API, added a security material for OAuth Authorization.Find your iFlow and copy the endpoint URL 🧪 Step 4: Test in Postman In Postman: Method: POST URL: Paste your endpoint Authorization: Basic Auth Use your Integration Suite credentials Headers: Content-Type: application/json Body (raw, JSON): json { “name”: “Pranjali”, “email”: “abc@example.com”, “message”: “Test from Postman!” } Click Send. 📈Step 5: Check the Results In SAP BTP: Go to Monitor → Monitor Message Processing Look for your iFlow execution Open the message to see: Payload trace Adapter logs Success or error details 🧠 Tips & Common Errors that you phase while deploying the iflow: Error Cause Fix 401 Unauthorized Wrong credentials or missing role Ensure ESBMessaging.send role is assigned 404 Not Found Incorrect endpoint Verify path /triggerEmail matches exactly Empty or broken payload Incorrect headers Add Content-Type: application/json Mail not received Mail adapter config issue Double-check SMTP host, port, and credentials Flow doesn’t appear in monitor Wrong trigger format Ensure JSON body is well-formed and matches iFlow expectations ✅Final Thoughts Testing your iFlows doesn’t need to be hard. Postman made it quick and easy for me to validate my flow and debug it. If you’re just getting started with SAP BTP Integration Suite, I highly recommend trying this out with a simple HTTP-to-Mail flow. Read More Technology Blog Posts by Members articles
#SAP
#SAPTechnologyblog
