API keys
API keys connect your tools to Trigv. You’ll need one for Zapier, GitHub Actions, scripts, and most integrations.
Step 1 — Open the dashboard
- Go to app.trigv.com and sign in.
- In the left sidebar, click API Keys.
Step 2 — Create a key
- Click Create API key (or similar).
- Give it a name you’ll recognize — e.g.
Zapier,GitHub CI,Home server. - Click create. Trigv shows the full key once.
- Copy it immediately and store it somewhere safe (password manager, GitHub secret, Zapier header).
You can’t view the full key again. If you lose it, rotate or revoke the old key and create a new one.
Step 3 — Use the key in your tool
Paste the key as a Bearer token — never in the message body:
Code
Authorization: Bearer trgv_abcd1234_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Each integration guide shows where to paste this (Zapier header, GitHub secret, etc.).
Managing keys later
Back in API Keys on the dashboard you can:
- Rotate — invalidates the old key and gives you a new one
- Revoke — permanently disables a key
- Set expiry — optional, when creating a key
Good habits
- Use separate keys per tool or environment (production vs. testing).
- Never commit keys to git or paste them in public Zaps/screenshots.
- Rotate immediately if you think a key leaked.