Connect Your Workflow Using Outgoing Webhooks

While Webhook Integrations (aka "Incoming Webhooks") allow you to pull any data from any external data sources into Tonkean, Outgoing Webhooks allow you to integrate Tonkean from the other side - triggering and sending data to other tools.
With Outgoing Webhooks, Tonkean is configured to “call” your webhook when certain events happen in Tonkean; i.e. a Track was created/updated or a user provided context to a data change. At its core, this capability is similar to the two-way sync functionality in our native integrations and third-party tools to be updated from within Tonkean. 
It can do much more than that, too!

Using a simple Zapier integration, for example, Tonkean can trigger a full internal workflow directly from within the Board - and the Tonkean A.I. Bot.

With Tonkean’s smart and proactive followup engine, custom workflows can be activated when important data changes, or when something is blocked. It’s all automated and fully managed by the Tonkean A.I. Bot.


Create a New Outgoing Webhook

In your Tonkean List, click Actions and select Outgoing Webhooks.

Then create an Outgoing Webhook:

Choose a name and select the activities that should trigger your webhook.

In the Webhook URL enter your Webhook/API URL for Tonkean to call.

You Webhook URL must conform to the following:

  1. Accept HTTP POST
  2. Accept JSON Content-Type
  3. Require no authentication

Click on the "Example" link to see a JSON example of what will be sent.

When you are done, click " Create."


That's it.

Now, every time an activity on that specific List triggers (i.e. a Track was created), Tonkean will send to the URL you specified a JSON of the Track in question and a log of the changes that triggered the event.

To read more and see an example use case, check out this blog post.