Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.
This step-by-step guide will show you how to create a powerful workflow with webMethods.io Integration. This workflow automatically sends a notification to your chosen Webex Teams space whenever a new Stripe customer is created.
Select New customer and complete the authorization – connect webMethods.io Integration with your Stripe account. You need to provide an API key - you can find it in the Developers settings in your Stripe account under the API keys tab.
Click Save. You should see the test trigger window.
To test your trigger, you need to perform the trigger action. Open your Stripe instance and add a new customer:
Go back to the webMethods.io Integration workflow and click Test. You should see the output data from the trigger which webMethods.io Integration will use to configure and test the rest of the workflow. Click Done.
Add the Cisco Webex Teams connector to the canvas with the drag and drop feature. This automatically connects with the previous step
Click on the small settings icon on the Cisco Webex Teams connector, select Post new message as action and complete the authorization – connect webMethods.io Integration with your Cisco Webex Teams account.
Now you can proceed with the action configuration – choose the Space ID where you want to post the message. Type the message body – use the Incoming data panel to include customer information received from the trigger output, for example:
New customer in Stripe: Email - {{$trigger.email}} First and last name - {{$trigger.name}}
Click Next and then Done.
You can now run the workflow using the play button in the right upper corner and review the result. If you have configured the workflow correctly, you should see the newly created message in your Cisco Webex Teams space:
From here you can monitor the executions status and view error details if needed:
Please note that workflow execution logs must be enabled from the workflow execution settings: