If you don't see an Aha! Roadmaps integration with your tool of choice, you can use an activity webhook to send workspace or account data to a third-party tool.
Activity webhooks do not send all data for a record when a field is updated. They only send over the fields that were updated.
Click any of the following links to skip ahead:
Enable the integration
You can create activity webhook integrations at either the account- or workspace-level by navigating to Settings ⚙️→ Account → Integrations or Settings ⚙️→ Workspace → Integrations, respectively. Administrators with customization privileges can create account-level integrations, and workspace owners can create workspace-level integrations.
At either level, the process is largely the same.
Select Activity webhook from the list of available integrations.
Enter the Hook URL for your webhook.
Select which activity Aha! Roadmaps should send through the activity webhook. At the account level, choose from Workspaces, Record types, and Fields. At the workspace level, choose from Record types, and Fields. Click Add activity to add the activity, and the large X to remove an activity from the list.
Select which users' activity will be transmitted through the webhook. This is an optional step, useful if you only want to send activity related to certain users. Click Add user to add a user's activity to the list, and the large X to remove a user's activity from the list.
Click the Enable checkbox, and add the webhook to your third-party tool to begin sending activity out of your Aha! Roadmaps account.
All activity waits five minutes before posting to the Activity webhook. This is to keep communication concise and avoid excessive messaging when a user is performing multiple edits at once. Check the box next to Deliver immediately to bypass the five minute delay.
Authentication
Activity webhooks coming from your Aha! account are encrypted via SSL. This can be used to verify the authenticity of any requests.
Troubleshoot
Having trouble with your activity webhook? Click Log messages below the webhook's integration settings to open the integration's audit log and use the log messages to diagnose and fix the problem.