Zapier, Make and automations

What you can automate

• Start something elsewhere when feedback arrives, a task changes status or someone replies.
• Create a CommentKit task from another tool, for example a form or a support ticket.

Both work with an agent token that has the Create tasks and add webhooks (Zapier) permission. Create it in Project → Developers; the project ID is shown next to it. Only workspace owners and admins can create one.

The token keeps working while the automation runs: every request and every delivered event keeps it for another 90 days. After 90 days without use it ends. We email the person who created it and the workspace owner a week and a day before, and when it ends its webhooks are turned off, not deleted. Removing someone from the workspace deletes the tokens and webhooks they added.

Zapier

The CommentKit Zapier app has the triggers New Feedback or Task, Task Status Changed and New Reply, the actions Create Task and Reply to a Task, and the search Find Task. Connect it with the agent token as the API key and your project ID.

The app is not in the public Zapier directory yet. Ask us at [email protected] for an invite link. Turning a Zap on adds a webhook to the project; turning it off removes it again.

Make, n8n and others

Any tool that can receive a webhook or send an HTTP request works:

• Receive events: add the tool’s webhook address in Project → Developers → Webhooks, or subscribe from the tool with POST /api/v1/agent/projects/{project}/hooks (url and events). Check the signature as described in webhooks.
• Create tasks: POST /api/v1/agent/projects/{project}/tasks with a title, sent with Authorization: Bearer and your agent token from the tool’s server, never from a web page.

A project has at most 10 webhooks, including the ones automations add (too_many_webhooks). Details are in the API reference.