Automate running an AAC Plan with the AAC API
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Notify Moderator
on 05-13-2024 11:32 AM - edited on 06-04-2024 10:37 AM by baileykaplan
Overview
This tutorial explains how to connect Workato and Alteryx to run each others recipes or plans respectively. This is just 1 example of how an Alteryx Analytics Cloud (AAC) Plan can connect with another data analytics tool to work in a coordinated fashion with your data.
Run an AAC Plan via API
Running an AAC Plan via API from Workato or Similar Tools
-
Get an API access token from the AAC workspace that contains the plan you want to run.
-
You can follow the guide here: https://alteryx.atlassian.net/wiki/spaces/EX/pages/2214723814
-
-
Call the /v4/plans/{id}/run endpoint from Workato or a similar tool that can hit API endpoints. Set it up similar to a curl command like this:
-
Documentation on this endpoint: https://us1.alteryxcloud.com/documentation/api#operation/runPlan
-
Replace {id} and <token> with your own plan's ID and API access token respectively.
curl -X POST 'https://us1.alteryxcloud.com/v4/plans/{id}/run' \ -H 'Content-type: application/json' \ -H 'Authorization: Bearer <token>'
-
Video Demo
Call an API from AAC Plans
Running a Workato Recipe or Similar Tool from an AAC Plan
-
Determine the endpoint or webhook you want to call to hit Workato or the tool you want to connect to an AAC plan.
-
In this case it is https://webhooks.workato.com/webhooks/rest/{id of recipe}.
-
Documentation on it here.
-
-
Create a plan in your AAC workspace.
-
Add an HTTP task to your plan and a post method to hit the Workato webhook and kick off the recipe.
-
Your plan will run the workflows it needs and then it will prompt the Workato Recipe (or similar tool) to kick off its actions.
Video Demo
Summary
In this tutorial, we’ve shown how you can automatically run another data analytics tool in tandem with Alteryx.
Thank you for reading along and if you have issues or questions feel free to comment them below or post in the Developer Discussion Forum!