Zapier
5,000+ apps. Comprehensive coverage across every KnoxCall resource.
Make
Visual scenarios. Full module coverage across every KnoxCall resource.
n8n
Self-hostable, open-source. Community node with full module coverage.
What makes these connectors different
Most “secrets” integrations just read and write values. KnoxCall’s connectors are built so the secret never has to enter the automation platform:- Proxy a Request — call any third-party API through KnoxCall. Reference stored
secrets and vault tokens with
{{token: ...}}placeholders; the real values are injected server-side. Your API keys never touch Zapier/Make/n8n. - Tokenize / Detokenize — swap PII (card numbers, SSNs, emails) for vault tokens so raw values never sit in an automation’s data store.
- Encrypt / Decrypt / Sign / JWT — encryption-as-a-service from a single step.
- Issue short-lived DB credentials and certificates on demand.
Authentication (all platforms)
Every connector authenticates with OAuth client credentials. In KnoxCall, go to Security → API credentials and create an OAuth client; copy its Client ID and Client Secret into the connector along with your Environment (Production or Sandbox). The connector exchanges them for a short-lived token and auto-discovers your tenant — you never type your slug.DPoP (sender-constrained tokens) is not used by these connectors. If your OAuth client
requires DPoP, the connector will tell you — disable DPoP on that client or use a
different one.
Triggers
Triggers are powered by KnoxCall webhooks. Subscribe to the request lifecycle (request.success, request.error, request.client_error, …) or to audit.event to
stream every audit-log entry into Slack, a SIEM, or a spreadsheet. Deliveries are
HMAC-signed; the connectors verify the signature for you.