All Collections
Common Problems with Hypercontext app integration with Zapier
Common Problems with Hypercontext app integration with Zapier
Ganindu Porage avatar
Written by Ganindu Porage
Updated over a week ago

My API Key isn’t working:

If you haven’t already generated an API KEY, tap ‘Generate new API key’. Note: This is a private API KEY that will allow Zapier access to your Hypercontext account so do not share this key.

You can always generate a new key by selecting ‘Generate new API key’. By doing this, any previous Zaps you have configured will no longer work until you update the API KEY in the Zap’s settings on Zapier.

Closing a Next Step/Next Step Formatting:

If you would like to have another application close off next steps in Hypercontext, you’ll need to add the Next Step ID to the body of the content being sent into Hypercontext in a specific format: `next_step_id: ## `.

In the example below, the next step ID data was stored in the `notes` field from Asana. Specifying this as the location for the Next Step Data will create the connection.

A Next Step ID would only be available if you’ve set up the appropriate connection from Hypercontext to send next steps to other applications. A Hypercontext configured ZAP will always put the ‘next_step_id: ##’ in the main body of the third-party application payload. For specific help with setting up your Zap, please contact our support team.

Did this answer your question?