Automations: HTTP Post
The HTTP Post Automation enables Dado to automatically make a Post call to an endpoint of your choice, with the authentication and data payload you set.
Setting up the HTTP Post Automation
Troubleshooting the HTTP Post Automation
Setting up the HTTP Post Automation
Create your Automation and add this Action
Go to the edit view of the Experience where you'd like to add this Automation, and go to the Timeline settings. Click on the rough position in the Timeline where you'd like to add the Automation, and select Automation in the modal that appears. This will bring you to the Automation edit screen.
Drag the HTTP Post Automation across from the right hand column to the center column.
Add the endpoint and authentication settings
The settings for this Automation will appear in the right hand column.
Add the URL you'd like Dado to post to in the first box. You can insert variables (eg employee ID) into this path, by clicking the plus icon in the right of the URL box.
Then select your preferred authentication option:
- None: we advise against using this if you'll be posting any employee data or triggering sensitive actions
- Basic Authentication: you will be asked to provide a username and password if you select this option
- Authorization Header: you will be asked to provide the header details if you select this option
Add your request body
Finally, add the payload you'll like to send, in JSON format, to the final box
Adjust the other Automation settings, if desired
- Be sure to give the Automation a meaningful title. This will only be visible in the dado admin interface, so choose something that will help you and your colleagues remember what this Automation does.
- Adjust the timing of the Automation – either starting on a specific timeline day, or after completion of a Task in the Experience.
- Add Target Audiences so the Automation will only fire for specific subgroups of your employees.
Save your Automation and your Experience
When you're happy with the Automation settings, click the blue Save button at the top right of the window, then close this window and click Save changes at the bottom right of the timeline.
Troubleshooting the HTTP Post Automation
When something goes wrong with the Automation, you will most often see an issue in the Issues Bar. These issues can be:
- Authentication related: the authentication header or username/password aren't accepted by the API Dado is calling; or the API requires a different kind of authentication from what you'd selected
- Data related: the request body does not contain the data required, or is not in the required format
- URL related: the URL you've specified does not exist eg because it includes a typo; or this endpoint will not accept post requests
If the Automation did not run when it shoud have in an individual's Experience, then try checking the following:
- Timing: This applies if you have set the Automation to run on a particular date in the Experience.
- Go to the individual view of that Experience (by going to the Participants table and clicking on the Participant's name) and search for the Automation. Is the run date still in the future?
- You can move the Automation to run on a different date, following these instructions.
- Triggering Task not yet completed: This applies if you have set the Automation to run when another Task in the Experience is completed.
- Go to the individual view of that Experience (by going to the Participants table and clicking on the Participant's name) and search for the Task which should trigger this Automation.
- If the Task is not yet completed, or skipped, this is why the Automation has not run. The Task must be completed to trigger the Automation.
- Target Audience excludes this individual: This applies if you have set one or more Target Audiences on this Automation
- Go to the timeline section in the edit view of the Experience. Open the Automation and check the Target Audience settings. Either the Target Audience has been set up incorrectly; or the person in question does not have the correct data to fall into this Target Audience
- Relating to when you added the Automation: the Automation will only appear in Experiences where its position on the timeline is still in the future
- For instance: you added the Automation on day 5 of the Experience. No one who has already passed day 5 will get this Automation.