Connect CortexDB to Make.com (formerly Integromat) workflow automations.
Make.com Integration
CortexDB integrates with Make.com (formerly Integromat) to bring long-term memory to your visual automation workflows. Use the HTTP module to call CortexDB's REST API, or import the pre-built app module definitions.
Setup with HTTP Module
The fastest way to use CortexDB in Make.com is via the HTTP module.
1. Create a Connection
In your Make.com scenario:
- Add an HTTP > Make a request module
- Click Add next to the Connection field
- Configure:
- Connection name: CortexDB
- Base URL: Your CortexDB server URL (e.g.,
https://api.cortexdb.ai)
2. Set Headers
For each HTTP module, add these headers:
| Header | Value |
|---|---|
| Content-Type | application/json |
| Authorization | Bearer YOUR_API_KEY |
Operations
Remember (Store Content)
HTTP Module Configuration:
- URL:
{{connection.base_url}}/v1/remember - Method:
POST - Body type: Raw (JSON)
{
"content": "The weekly sales meeting decided to increase Q2 targets by 15%.",
"tenant_id": "sales-team",
"scope": "meetings"
}
Recall (Retrieve Context)
HTTP Module Configuration:
- URL:
{{connection.base_url}}/v1/recall - Method:
POST - Body type: Raw (JSON)
{
"query": "What were the recent sales decisions?",
"tenant_id": "sales-team"
}
Forget (Remove Memories)
HTTP Module Configuration:
- URL:
{{connection.base_url}}/v1/forget - Method:
POST - Body type: Raw (JSON)
{
"query": "user data for [email protected]",
"reason": "GDPR deletion request",
"tenant_id": "default"
}
Search (Find Episodes)
HTTP Module Configuration:
- URL:
{{connection.base_url}}/v1/search - Method:
POST - Body type: Raw (JSON)
- Headers: Add
x-tenant-id: ops-team
{
"query": "deployment events",
"filters": {
"source": "ci-cd"
}
}
List Episodes (for Triggers)
HTTP Module Configuration:
- URL:
{{connection.base_url}}/v1/episodes - Method:
GET - Query parameters:
tenant_id:default
Example Scenarios
Google Sheets to CortexDB Memory
- Watch Rows (Google Sheets): Trigger on new rows
- HTTP Make a Request: POST to
/v1/remember- Content: Row data formatted as text
- Tenant:
spreadsheet-data
AI Chat with Memory (using Webhooks)
- Webhook: Receive incoming chat message
- HTTP Make a Request: POST to
/v1/recall- Query:
{{webhook.message}}
- Query:
- HTTP Make a Request: POST to OpenAI API
- Include recalled context in the prompt
- HTTP Make a Request: POST to
/v1/remember- Store the conversation exchange
- Webhook Response: Return the AI response
Scheduled Memory Cleanup
- Schedule: Run weekly
- HTTP Make a Request: POST to
/v1/forget- Query: Stale data criteria
- Reason:
Weekly cleanup
Slack Integration with Memory
- Watch Messages (Slack): New messages in a channel
- Router: Filter important messages (e.g., containing keywords)
- HTTP Make a Request: POST to
/v1/remember- Content:
{{slack.text}} - Scope:
slack
- Content:
Using the Custom App Definition
For advanced users, import the CortexDB app definition:
- In Make.com, go to My Apps > Create a New App
- Use the app definition from the
cortexdb-makepackage - The app includes pre-configured modules for all CortexDB operations
REST API Reference
| Endpoint | Method | Description |
|---|---|---|
| /v1/remember | POST | Store content in memory |
| /v1/recall | POST | Retrieve relevant context |
| /v1/forget | POST | Remove memories |
| /v1/search | POST | Search for episodes |
| /v1/episodes | GET | List recent episodes |
| /v1/admin/health | GET | Health check |
Tips
- Use variables: Reference data from previous modules using Make.com's mapping panel
- Error handling: Add error handlers to your HTTP modules to gracefully handle CortexDB downtime
- Rate limiting: CortexDB handles concurrent requests well, but add a delay between bulk operations
- JSON parsing: After each HTTP module, use a JSON > Parse JSON module to extract response fields
Under the Hood
All Make.com HTTP modules call the CortexDB REST API directly. See the operation examples above for the exact request format.