Skip to content
threada Docs

Zapier setup and support

Threada for Zapier lets a Zap create or update governed Threada WorkItems through the public API. The first public app is intentionally action-only: it can create a WorkItem, append a human-readable WorkItem message, and update accepted WorkItem routing or lifecycle fields. It does not execute third-party actions, bypass approvals, poll for WorkItem changes, or expose destructive operations.

This guide supports private Zapier reviewer testing now and public Zapier users after the integration is approved and listed.

Start Threada-side runtime setup from https://studio.threada.ai/integrations/zapier/install when a reviewer or tenant admin needs to bind the Zapier runtime integration record to a pack. The Zapier app itself still connects from Zapier to Threada with a tenant-scoped Threada API key stored in Zapier’s connected-account credential store.

Requirements

Before connecting Zapier, make sure you have:

  • An active Threada tenant.
  • Admin access in Threada to create and revoke tenant API keys.
  • A Zapier account with access to the private Threada integration invite, or the public Threada app after Zapier approval.
  • A tenant-scoped Threada API key with the smallest scopes needed:
    • work.read for Zapier’s connection test.
    • work.write for Create WorkItem, Append WorkItem Message, and Update WorkItem.

Do not use a key with work.actions for the Zapier v1 app. Zapier v1 does not create, approve, or execute action proposals.

Create a Threada API key

  1. Sign in to Threada as a tenant admin.
  2. Open the Admin governance API-key surface.
  3. Create a key for Zapier with work.read and work.write.
  4. Copy the one-time secret and store it in your password manager until you finish connecting Zapier.
  5. Record a non-sensitive label, such as the tenant or workspace name. Do not store the API key in the label.

The secret is shown only once. If you lose it, revoke the key and create a new one.

Connect Threada in Zapier

  1. In Zapier, create or edit a Zap and add a Threada action step.
  2. Choose Connect a new account.
  3. Paste the Threada API key into the authentication field.
  4. Optionally enter a workspace label so admins can tell connections apart.
  5. Test the connection. Zapier checks the public WorkItems list endpoint with the API key.
  6. Save the connected account.

The Zapier app uses Threada’s production public API at https://api.threada.ai. Public Zapier versions must not use dev, staging, sandbox, or localhost endpoints.

Create a WorkItem

Use Create WorkItem when a Zap should open a new governed record in Threada.

Required fields:

  • Subject: short WorkItem title.
  • Initial message: the request or context users should review in Threada.

Optional fields include priority, queue, tags, source references, and contact details. Zapier-created WorkItems use the custom channel and store Zapier provenance in source labels and references rather than inventing a new channel type.

The action returns structured fields, including WorkItem ID, subject, status, priority, channel, queue, assignee fields, and timestamps. Use the WorkItem ID in later Zap steps when appending messages or updating the WorkItem.

Append a WorkItem message

Use Append WorkItem Message when a later Zap step should add a human-readable note to an existing WorkItem.

Required fields:

  • WorkItem ID: the ID returned by Create WorkItem or another trusted source.
  • Message content: the note to add.

Do not append raw third-party event dumps, secrets, cookies, tokens, or customer exports. Keep the message useful to the human reviewing the WorkItem.

Update a WorkItem

Use Update WorkItem to update only the fields accepted by the live public API:

  • Status.
  • Queue.
  • Assignee ID.
  • Assignee name.

At least one mutable field is required. The Zapier v1 app does not update subject, priority, tags, evidence, or action-execution fields.

What Zapier v1 does not do

The first Zapier app does not include triggers. New WorkItem and Updated WorkItem triggers remain blocked until Threada exposes Zapier-safe polling, recency, cursor, or webhook semantics that prevent missed updates and noisy duplicates.

The first Zapier app also does not execute external actions. If a workflow needs to update Jira, Zendesk, HubSpot, Salesforce, ServiceNow, or another connected system, keep that side effect inside Threada’s governed action proposal, approval, idempotency, and audit flow.

Troubleshooting

If Zapier cannot connect to Threada:

  • Confirm the API key was pasted into the authentication field, not an action input field.
  • Confirm the key has work.read.
  • Confirm the key has not been revoked.
  • Create a new key if the one-time secret was lost.

If a Zap action fails:

  • For Create WorkItem, confirm Subject and Initial message are present.
  • For Append WorkItem Message, confirm the WorkItem ID exists in the same Threada tenant and Message content is not blank.
  • For Update WorkItem, confirm at least one supported mutable field is present.
  • For permission errors, confirm the key has work.write.
  • For rate-limit or temporary service errors, retry after a minute and check the Zap run history for the exact error code.

Do not send API keys, Zapier credentials, raw payload exports, cookies, or customer data to support.

Rotate or revoke access

To rotate the Zapier API key:

  1. Create a new Threada API key with work.read and work.write.
  2. In Zapier, reconnect or update the Threada connected account with the new key.
  3. Test a Zap step.
  4. Revoke the old key in Threada Admin.

To disconnect Zapier, remove the Threada connected account in Zapier and revoke the corresponding API key in Threada Admin. Existing WorkItems, messages, approvals, and audit events remain in Threada according to the tenant retention policy.

Data handling

Zapier sends the field values configured in each Zap action to Threada’s public API. Threada stores those values on tenant-scoped WorkItems, messages, and audit records according to the tenant’s retention settings.

Threada does not use Zapier payloads to train large language models. Threada does not receive Zapier account credentials. Zapier stores the Threada API key inside Zapier’s connected-account credential store and sends it to Threada in the X-Api-Key header when a Zap step runs.

For privacy or deletion requests, contact privacy@threada.ai. For support requests, contact support@threada.ai. To report a security issue, contact security@threada.ai.

Support requests for the Zapier app receive a response within 2 business days.