Why won't my Trigify API key verify in Clay (or another tool)?

If you’re connecting Trigify to Clay, Make, n8n, or any other tool and the key won’t verify, this article walks through getting a valid key and the two most common reasons verification fails.

Where to find your API key

  1. Open Settings → API Keys in the Trigify app.
  2. Create a key if you don’t have one, and copy it. Trigify API keys start with trig_.

Copy the key in full, including the trig_ prefix, and don’t add spaces or line breaks. A truncated or partial key is the single most common cause of “Could not verify.”

How to send the key

Trigify accepts the key two ways — use whichever your tool asks for:

Method

What to send

API key header

x-api-key header with your key

Bearer token

Authorization header, Bearer + your key

In Clay, paste the trig_… key into the Trigify API key field — Clay sends it for you.

If it still won’t verify

There are two usual causes:

  • Wrong or partial key — regenerate it in Settings → API Keys and paste the whole thing again.
  • Your subscription isn’t active — the API rejects keys when the workspace subscription isn’t active (see Why am I getting “User does not have a subscription” on API calls?). Check Settings → Manage Plan.