In this article, you'll learn how to add an Action step to your Flow.
Please read the article about Guided Flows to have a head start on why an Action is added to a Guided Flow.
Adding an Action Step to a Guided Flow
As an example, we will be using the Mailchimp app as an Action app and Sendinblue as the Trigger app. The Guided Flow we're creating in this example works the following way:
Every time a new contact is created in Sendinblue, a subscriber for it is added in Mailchimp.
Let's get started.
After adding the Trigger step, you will be asked to add an Action step as a child step.
Step 1: Add the App Connector for the Action app.
Search and add the Action app from this menu. As an example, we will add the MailChimp App Connector to our Guided Flow. This means that an Action will be performed on MailChimp once Integry receives a Trigger from Sendinblue.
Step 2: Select the action to be performed on the Action app.
Click on Select an action or query for this step and select an action operation from the Activity dropdown.
For example, we will select Create Subscriber as an action because we want to sync contacts from the Sendinblue account to the MailChimp account.
This would mean that a new subscriber will be automatically created in the MailChimp account whenever the end-user creates a contact in the Sendinblue account.
Step 3: The next step is to connect your action app account.
Select an already added account or add a new one by clicking on 'Add My Account.' The account you select here will be used by Integry to access the Action app to carry out the action.
For example, we added a MailChimp end-user account in this step. A new subscriber will be added to this account upon the execution of the Flow.
Configuring the Fields for the Action Step
Step 4: In the next step, turn the User Visible Form toggle on to configure the fields of the action app. The configurations you do here will reflect on the Guided Flow setup form visible to the end-users. The configuration of Action step fields are similar to the configuration of the Trigger step fields.
We will configure the following fields for the Mailchimp app.
The first field that we will configure is the List field. This is the list where a new subscriber will be added as a result of this integration. The end-user trying to set up this integration will be able to add their own list here.
Next, we will configure the subscriber's email address.
As we want the same contact details from the trigger app to be reflected in the action app, we will add the email field of the trigger app here.
These fields are app-specific, the configuration you'll do in this step will depend on your trigger and action applications.
Step 5: Map the corresponding fields of both apps.
Testing the Action Step
Next, you'll have to test your Action step to see if the integration flow is being executed successfully.
Step 7: Select the sample values for your fields and click on the 'Test' button (shown above). Similar to the Trigger step testing, the Flow will be saved when you start testing.
Click on Test Result to check the response of the API call made to the action API.
Integry makes a POST call to action API with the payload containing the contact information. As a response of the request call, the action app sends back the information of the subscriber added as a result of the integration. (shown above)
Click on 'Done' if your Guided Flow works as intended.
Click on '+ Add Step' and add as many steps to your Flow as you want.
Previewing the Guided Flow
Preview how your Guided Flow will appear for your end-user when they're setting up this integration.
Step 8: Click on the 'Preview' button, shown above.
If the end-user is setting up this integration natively from your app and implicit auth is configured on your SDK deployment, this step will not be shown to them. Similarly, this step is hidden from the end-users who are logged into your app and setting up this integration from your Integration Marketplace and Single Sign-On is implemented on your Marketplace.
Since we are in the preview mode, this step will be visible to us.
Add the trigger application account and click on 'Next' to continue.
Then, we'll select the List that we configured for our Trigger app step and click on 'Next.'
Similarly, we'll connect our action application account and click on 'Next.'
Again, this step is only visible to us in the preview mode and hidden to the end-user if:
- Implicit auth is configured on your SDK Deployment.
- Or, SSO is implemented on your Marketplace Deployment
Next, the action application configuration step appears in the Guided Flow where the end-users can configure and map their fields.
Remember, the configuration and setup of a Guided Flow for an end-user depends on how you design it using the Guided Flow Builder.
Once you're satisfied with your Guided Flow's configuration, go back to the Flow Builder to save and publish your Flow.
Step 9: Click on 'Save' to save your Flow.
Step 10: To deploy your Flow on your Marketplace or SDK, click on 'Publish Flow.'
Choose a Deployment from the dropdown menu and click on 'Done.'
You're all done creating and testing your Guided Flow.