Integrations

Rekor isn't a closed system — it's designed to sit between your agents and external services. Five integration primitives handle data flowing in, data flowing out, bulk operations, external API proxying, and AI provider compatibility.

Which Integration Do You Need?

You want to...	Use
Receive data from an external system (GitHub, Stripe, PagerDuty)	Hooks
Notify an external system when data changes in Rekor	Triggers
Create many records, relationships, or collections atomically	Batch Operations
Let agents read/write an external API through Rekor's tools	External Sources
Import/export tool definitions for OpenAI, Anthropic, Google, MCP	Provider Adapters

Data Flow

Think of it as three directions:

• Inbound — external systems push data into Rekor via hooks. Each hook exposes a unique URL that accepts POST requests and creates records in a target collection.
• Outbound — Rekor pushes change notifications to external systems via triggers. Triggers fire asynchronously after record creates, updates, or deletes.
• Bidirectional — external sources proxy reads and writes to any REST API. The agent uses the same Rekor tools — it doesn't know whether data lives locally or in Stripe, Salesforce, or your internal API.

Combining Integrations

Integrations compose naturally. A common pattern:

1. A hook receives a Stripe invoice webhook
2. Rekor creates a record in the invoices collection
3. A trigger fires and notifies Slack about the new invoice
4. An agent queries invoices through the sql_query tool

Loop prevention is built in: writes that originated from hooks carry a marker, and triggers skip hook-originated writes by default.

Environment Restrictions

Hooks, triggers, and external source configs can only be created in preview workspaces. To add them to production, configure in preview and promote. Secrets are regenerated on the production side during promotion — preview secrets are never copied.

All Integration Types