> ## Documentation Index
> Fetch the complete documentation index at: https://docs.knoxcall.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Zapier

> Use KnoxCall in Zapier Zaps

The KnoxCall Zapier app connects KnoxCall to 5,000+ apps with comprehensive coverage of
every KnoxCall resource.

## Connect your account

1. Add a KnoxCall step to a Zap and choose **Connect a new account**.
2. Pick your **Environment** (Production or Sandbox).
3. Paste the **Client ID** and **Client Secret** from KnoxCall → **Security → API
   credentials**.
4. Zapier verifies the connection and labels it with your tenant slug.

## Triggers

**Instant** (delivered the moment an event happens):

* New Completed / Successful / Failed Request, plus 4xx, 5xx, received, redirect, and
  timeout variants — optionally filtered to a single route.
* **New Audit Event (SIEM)** — every config change, auth event, and rotation.

**Polling** (checked on a schedule): New Audit Log, New Route, New Secret, New Database
Credential Lease, New Webhook Delivery.

## Actions

The headline, security-forward actions:

* **Proxy a Request (inject secrets)** — call any API through KnoxCall with
  `{{token: TOKEN_ID}}` placeholders resolved server-side.
* **Tokenize / Bulk Tokenize / Detokenize** — keep PII out of your Zaps.
* **Encrypt / Decrypt / Sign / Sign JWT** — managed cryptography.
* **Issue / Revoke Database Credential**, **Issue / Revoke Certificate**, **Rotate OAuth
  Client Secret**, **Create / Set Secret**.

Plus full CRUD across routes, secrets, vaults, crypto keys, PKI, dynamic DB credentials,
webhooks, clients, environments, OAuth clients, API keys, and agents.

## Searches

Find Route, Find Secret, Get OAuth2 Secret Token, Get Crypto Public Key, List Audit Logs,
Get Account / Usage, and more — handy for lookups inside a Zap.

## Example: tokenize a card number before storing it

1. **Trigger:** New row in your form/CRM app.
2. **KnoxCall → Tokenize a Value** — vault `cards`, value = the card number.
3. **Store** the returned token (not the raw number) in your database.
4. Later, **KnoxCall → Proxy a Request** to your payment processor with
   `{{token: TOKEN_ID}}` in the body — the real number is injected only at the edge.