Zapier (coming soon)

Trakkr's Zapier integration turns changes in AI visibility into steps in the tools your team already uses. A completed report can start a reporting workflow. A priority action can become a task or message. A form response or research list can add a tracked prompt to the right brand.

The integration uses polling triggers, so you do not need to configure a webhook or copy an API key.

Before you connect

You need:

• A paid Trakkr brand with integration access
• A Trakkr user who can view that brand
• Editor access if the Zap will create a prompt or complete an action
• A Zapier account that can create and run the Zap you need

Brand access comes from your current Trakkr membership, team grant, or active client assignment. Connecting Zapier does not grant access to another brand. Client portal access is read-only for this integration and cannot run either write action.

Connect Trakkr to Zapier

1. 1.Add a Trakkr trigger or action to a Zap.
2. 2.Choose Connect a new account.
3. 3.Zapier opens Trakkr's authorization page over HTTPS.
4. 4.Sign in to Trakkr if needed, review the connection, then approve it.
5. 5.Return to Zapier and confirm that the connection label shows the expected Trakkr email address.
6. 6.Choose a brand in the Zap step and test it with sample data.

Zapier stores the short-lived OAuth access token and rotating refresh token. The token uses Trakkr's dedicated Zapier scope and cannot call Trakkr's hosted MCP tools. It does not receive your Trakkr password. You can revoke the connection from Trakkr or remove it from Zapier.

Triggers, searches, and actions

All triggers return the newest matching records first, up to 100 per poll. Zapier remembers each trigger's primary event ID and does not run an unchanged event twice.

Useful Zap patterns

Send priority actions to your task system

Use New or Updated Priority Action as the trigger, then map title, description, priority_level, priority_score, and url into the task app. Store action_id if you want a later Zap to find or complete the same Trakkr action.

Add visibility snapshots to a reporting sheet

Use New Visibility Snapshot, then add visibility, presence, average_rank, mentions, models_mentioned, and created_at as columns in your reporting destination.

Notify a team when a report is ready

Use Report Ready, then send report_name, report_type, time_range, and url to email or chat. The recipient must sign in to Trakkr and have access to the brand to open the report page.

Add approved research questions as prompts

Use Create Tracked Prompt after an approval, form, or research step. Pick the editable Trakkr brand, map the question into Prompt, and leave Start Tracking on when it should enter the active prompt set.

Permissions and data safety

Read steps check the connected user's current effective brand access and the selected feature entitlement. Write steps also require editor access, a paid brand, and direct brand authority rather than client portal authority.

Trakkr binds every action or prompt to the brand chosen in the Zap step. An action ID from another brand does not reveal whether that action exists. API responses do not include OAuth tokens, passwords, internal stack traces, report storage URLs, or Trakkr service credentials.

Troubleshooting

The brand is missing

Check that the connected Trakkr user still has access to the brand. Reconnect the account if its membership changed recently, then reload the brand field in Zapier.

A trigger returns no samples

Confirm the selected brand has a matching completed or open record:

• Priority actions must be open and high priority, critical, pinned, or scored 70 or above.
• Visibility snapshots must have completed successfully.
• Generated reports must be complete, active, and not deleted.

A create or complete step is forbidden

The connected user needs editor access to the selected brand. Client portal access and viewer access cannot write. A paused subscription or missing integration entitlement can also block the step.

The connection expired

Zapier normally refreshes an expired access token once. If the connection was revoked or refresh fails, reconnect the Trakkr account in Zapier.

The Zap is waiting to retry

Trakkr allows up to 120 reads and 30 writes per connected user per minute for this integration. A 429 response includes Retry-After, which tells Zapier when to try again.

If the problem continues, contact Trakkr support with the Zap step name, approximate time, selected brand name, and Zapier request ID. Do not send passwords, OAuth tokens, or client secrets.

API reference for the official Zapier integration

The official integration calls https://api.trakkr.ai/zapier/v1 over HTTPS. These endpoints accept a Trakkr OAuth bearer token with the exact zapier:integration scope issued to the registered Zapier client. They reject MCP and other partner tokens, and they do not accept Trakkr API keys.

Create a tracked prompt

POST /prompts

{
  "brand_id": "brand UUID",
  "text": "Which tools improve AI visibility?",
  "active": true
}

An exact same-text retry in the same brand returns the existing prompt with created: false.

Complete an action

POST /actions/complete

{
  "brand_id": "brand UUID",
  "action_id": "action UUID",
  "note": "Optional completion context"
}

The note is optional and limited to 2,000 characters. A repeated completion returns the current action with replayed: true.

API responses

OAuth credentials belong in Zapier's authentication configuration. Never put an access token, refresh token, client ID, or client secret into a trigger, search, or action field.