Manual Integrations are different from automated workflows, as these integrations require the user to start them. In a regular template, the integration works automatically after a trigger occurs. But manual integrations do not wait for a trigger to happen. Instead, the user’s initial input triggers the integration. A manual integration is mostly a part of another template i.e., a template within another template.
Say that you are syncing tasks in your app with another task manager like Jira. You might want to push a few selective tasks to Jira and not sync all the items in the list. For this, you will have a manual functionality like a “push task to Jira” button with each task. Clicking on this for any task will trigger the integration and sync it with Jira. This is how the user gets the ability to select the items and the app they want to perform the action in, for any trigger in real-time
Manual template within a template
Manual templates are most commonly used inside other templates. This is for when a user wants to perform an action while setting up an integration. This action gets completed within the integration setup screen before the user activates the integration.
Let’s say that you are creating an integration with the use-case, “when a subscriber is added to MailChimp, a new contact is created in your Sendinblue list”. While creating the integration, the user needs to select a contact list in their Sendinblue account where the contact will be created. In many cases, the user may not have a List set up yet. So, instead of making the user quit their flow to create the list, you can have them create the list right within the integration setup flow with a manual integration.
The Create List action is added as manual integration in the original template.
If the user wants to create a new list, they’ll select the option shown above and the following menu will appear.
The user will enter the name of the list and select a folder in Sendinblue where the list will be created. As soon as the user clicks the Save button, the manual integration will be saved and the “Create List” action will be performed in their Sendinblue account i.e. a new list will be created right away. The user will then be able to see the new list in the drop-down Select a list dropdown as well. After this, the user can continue with their integration creation process.
Adding manual templates inside template
Let’s see the above example from the template’s side. For the create list action, a manual template will need to be created first. You can create a manual template just like any other template on Integry. For list creation, the template should consist of only the following two steps.
The user input for creating the list is received as an incoming webhook to Integry. This webhook acts as the trigger in this manual template. The Create List action for Sendinblue is then performed as a result of the trigger.
A manual template like the above is added to the relevant steps of another template to be shown to the user. For our current example, the list step is a field that takes input from the user. This field is added inside the Adapter step that is visible to the user.
Inside the original template for Mailchimp’s sync with Sendinblue, the adapter step will have various fields that are visible to the user. The list selection fields should look like this:
Select a list is a section and Create a list is a tab within that section. The manual template should be added below the Create a list tab. This can be added from the UI/UX options that appear on the right side of any step you click. Use the Add Template button as shown below.
Once you click Add Template, another drop-down field will be added below the create list tab as shown below.
The drop-down list will display all the manual templates saved in your Integry account. From this list, you can select the one you created above for Sendinblue:
This will add the manual template in your original template, which appears at the exact location you want the user to find it. This will render the Create a list option for the user on the integration setup screen that has been talked about above in the article.