Connect CortexDB to 6,000+ apps with Zapier.

Zapier Integration

CortexDB's Zapier integration lets you connect long-term memory to 6,000+ apps. Store data from any trigger, recall context in multi-step Zaps, and search your memory from anywhere in your automation workflows.

Setup

  1. In Zapier, search for CortexDB in the app directory
  2. Click Connect and enter your CortexDB server URL and API key
  3. Test the connection

Actions

Remember

Store content in CortexDB's long-term memory.

Input Fields:

  • Content (required): The text to store
  • Tenant ID: Tenant identifier (default: "default")
  • Scope: Optional scope for organization

Example Use Cases:

  • Store form submissions from Typeform
  • Save Slack messages to long-term memory
  • Archive email content from Gmail
  • Log CRM updates from HubSpot

Forget

Remove memories from CortexDB.

Input Fields:

  • Query: Query to match memories for deletion
  • Reason: Reason for the operation
  • Tenant ID: Tenant identifier

Example Use Cases:

  • GDPR compliance: forget user data when a deletion request comes in
  • Clean up stale data on a schedule

Searches

Recall

Retrieve relevant context from CortexDB using natural language.

Input Fields:

  • Query (required): Natural language query
  • Tenant ID: Tenant identifier

Example Use Cases:

  • Enrich AI prompts with past context
  • Look up historical data before sending notifications
  • Provide context to support agents in Zendesk

Search Episodes

Search CortexDB for matching episodes with filters.

Input Fields:

  • Query (required): Search query
  • Tenant ID: Tenant identifier
  • Source Filter: Filter by episode source
  • Episode Type: Filter by type
  • Offset: Pagination offset

Triggers

New Episode

Fires when a new episode is added to CortexDB. Uses polling to check for new episodes.

Input Fields:

  • Tenant ID: Tenant to monitor

Example Use Cases:

  • Send a Slack notification when new knowledge is stored
  • Update a Google Sheet with new episodes
  • Trigger a follow-up workflow when memory changes

Example Zaps

Slack to CortexDB Memory

  1. Trigger: New message in Slack channel
  2. Action: CortexDB Remember
    • Content: {{message.text}}
    • Tenant ID: slack-team
    • Scope: slack

AI Support Agent with Memory

  1. Trigger: New ticket in Zendesk
  2. Search: CortexDB Recall
    • Query: {{ticket.subject}} {{ticket.description}}
    • Tenant ID: support
  3. Action: OpenAI Chat Completion
    • Prompt: Include recalled context + ticket details
  4. Action: CortexDB Remember
    • Content: Resolution summary
  5. Action: Update Zendesk ticket with AI response

Daily Knowledge Digest

  1. Trigger: Schedule (daily)
  2. Search: CortexDB Search Episodes
    • Query: important updates
    • Tenant ID: team
  3. Action: Send email digest via Gmail

REST API Reference

The Zapier integration uses the CortexDB REST API directly:

| Endpoint | Method | Description | |---|---|---| | /v1/remember | POST | Store content | | /v1/recall | POST | Retrieve context | | /v1/forget | POST | Remove memories | | /v1/search | POST | Search episodes | | /v1/episodes | GET | List episodes | | /v1/admin/health | GET | Health check |

Under the Hood

Each Zapier action/search maps to a CortexDB REST API call:

# Remember
curl -X POST https://api.cortexdb.ai/v1/remember \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"content": "Message text", "tenant_id": "slack-team"}'

# Recall
curl -X POST https://api.cortexdb.ai/v1/recall \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "ticket subject and description", "tenant_id": "support"}'

# Forget
curl -X POST https://api.cortexdb.ai/v1/forget \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "user data", "reason": "GDPR request", "tenant_id": "default"}'

# Search
curl -X POST https://api.cortexdb.ai/v1/search \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "x-tenant-id: team" \
  -d '{"query": "important updates"}'