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
- In Zapier, search for CortexDB in the app directory
- Click Connect and enter your CortexDB server URL and API key
- 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
- Metadata (JSON): Optional JSON metadata string
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
- Max Tokens: Maximum response size
- Min Confidence: Minimum confidence threshold
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
- Namespace: Filter by namespace
- Limit: Maximum results
- 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
- Trigger: New message in Slack channel
- Action: CortexDB Remember
- Content:
{{message.text}} - Tenant ID:
slack-team - Metadata:
{"channel": "{{channel.name}}", "user": "{{user.name}}"}
- Content:
AI Support Agent with Memory
- Trigger: New ticket in Zendesk
- Search: CortexDB Recall
- Query:
{{ticket.subject}} {{ticket.description}} - Tenant ID:
support
- Query:
- Action: OpenAI Chat Completion
- Prompt: Include recalled context + ticket details
- Action: CortexDB Remember
- Content: Resolution summary
- Action: Update Zendesk ticket with AI response
Daily Knowledge Digest
- Trigger: Schedule (daily)
- Search: CortexDB Search Episodes
- Query:
important updates - Tenant ID:
team - Limit:
10
- Query:
- 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/health | GET | Health check |