Zapier, Make and n8n: API key preset

For workspace owners. Zapier, Make and n8n connect to TweakTick with a workspace API key. A ready-made preset gives the key exactly the permissions these apps need, and nothing more.

Create the key

Open Settings → API.
Give the key a name you will recognise, such as "Zapier".
Choose the Zapier / Make / n8n preset.
Create the key and copy it. It is shown only once.
Paste it into Zapier, Make or n8n when they ask for your TweakTick key.

Use one key per app, so you can switch one off without breaking the others.

What the preset allows

Permission	Why the app needs it
`webhooks:write`	Start and stop the triggers (the app adds and removes its own webhook)
`projects:read`	Show your projects in the "Project" drop-down
`comments:read`	Load example events while you build a flow, and read comments (internal ones included)
`comments:write`	The actions: reply, resolve or reopen. A reply is internal (agency-only) unless the app asks for a client-visible one

A key with this preset can never approve a round, sign off, delete projects or comments, or email your clients.

A client-visible reply sent through the API is shown to your client but not emailed to them. Only replies you write in TweakTick send the "reply to you" email.
A new version started through the API emails nobody. The project page then shows Email clients about V2 (or the version number); press it once to send your clients the usual "new version ready" email and reminder.

What the apps get

Triggers never send internal (agency-only) comments, nor client emails, tokens or signed review links.
Reading comments through the API includes internal ones, because the key acts for a workspace owner. An app step that reads comments can see them, so keep internal notes out of steps that post where your client can see.

Plans

The API isn't part of the Free plan, so these apps need a paid plan or a workspace in early access. See billing and refunds. (The TweakTick Chrome extension's team mode is separate: it works on every plan, including Free, for any team member, and needs no API key. See the extension help.)

Revoking a key

Open Settings → API and revoke the key. Its triggers stop at once, and the app shows a connection error until you paste a new key.

Guides for each app

Create the key

Open Settings → API.

Give the key a name you will recognise, such as "Zapier".

Choose the Zapier / Make / n8n preset.

Create the key and copy it. It is shown only once.

Paste it into Zapier, Make or n8n when they ask for your TweakTick key.

Use one key per app, so you can switch one off without breaking the others.

What the preset allows

Permission	Why the app needs it
`webhooks:write`	Start and stop the triggers (the app adds and removes its own webhook)
`projects:read`	Show your projects in the "Project" drop-down
`comments:read`	Load example events while you build a flow, and read comments (internal ones included)
`comments:write`	The actions: reply, resolve or reopen. A reply is internal (agency-only) unless the app asks for a client-visible one

A key with this preset can never approve a round, sign off, delete projects or comments, or email your clients.

A client-visible reply sent through the API is shown to your client but not emailed to them. Only replies you write in TweakTick send the "reply to you" email.

A new version started through the API emails nobody. The project page then shows Email clients about V2 (or the version number); press it once to send your clients the usual "new version ready" email and reminder.

What the apps get

Triggers never send internal (agency-only) comments, nor client emails, tokens or signed review links.

Reading comments through the API includes internal ones, because the key acts for a workspace owner. An app step that reads comments can see them, so keep internal notes out of steps that post where your client can see.