[[{“value”:”
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 Package
- Enter Name: Mail_Testing
-
Add an Artifact to the Package
- Open the Mail_Testing package
- Click Create → Integration Flow
-
Configure the iFlow
- Name: Mail_Simple
- Click 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 Sender
- Add a Timer from the Event section
- Delete the Start element
-
Configure the Timer
- Open the Timer Scheduler
- Keep the configuration basic (default settings)
-
Add a Content Modifier
- Drag and drop a Content Modifier into the flow
- Configure Message Body:
- Type: Constant
- Value:
Hi All, This is for sample testing mail. Thanks & Regards,
-
Connect to Mail Receiver
- Connect the End of the flow to a Receiver
- Select Mail Adapter as the receiver type
-
Configure Mail Adapter Connection
- Address: smtp.gmail.com:587
- Protection: Optional
- Authentication: OAuth2 Authorization Code
- Credential Name: IS_GMAIL
-
Set Mail Processing Details
- From: Sender’s mail
- To: Receiver’s mail
- Subject: Testing
-
Save and Deploy
- Click Save
- Click 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 Create
- Select OAuth2 Authorization Code as the type.
-
Fill in Configuration Details
- Name: IS_GMAIL
- Description: Gmail configuration
- Provider: Generic
- Authorization URL: <authuri>?access_type=offline&prompt=consent
- Token URL: <authuri>/token
- Client ID: <clientid>
- Client Secret: <clientsecret>
- Send As: Basic Authentication Header
- Username: “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
#abap