Official Review & Module Specification
ChatCoat Make (Integromat) Integration
This guide specifies the connection architecture, OAuth 2.0 lifecycle, trigger iteration rules, and action specifications utilized by the official ChatCoat Make Custom App. All operations interact directly with ChatCoat's production cloud API.
1. Make Connection Settings
| Connection Type | OAuth 2.0 (Authorization Code with Refresh Tokens) |
| Authorize URL | https://social-automation-api-8a9h.onrender.com/oauth/authorize |
| Token URL | https://social-automation-api-8a9h.onrender.com/oauth/token |
| Refresh Token URL | https://social-automation-api-8a9h.onrender.com/oauth/token |
| Connection Test / Info URL | https://social-automation-api-8a9h.onrender.com/oauth/me |
| Make Redirect URI | https://www.make.com/oauth/cb/app |
2. Scopes Requested by Make Connection
Make requests only the minimum required scopes for lead management, campaign tracking, and continuous polling.
| Scope Key | Module Usage | Description |
|---|---|---|
| leads:read | Watch New Leads | Poll and retrieve leads captured across campaigns |
| leads:write | Create Lead | Insert new prospect records into the workspace |
| campaigns:read | Campaign Reference / Universal | Verify associated campaign targets |
| offline_access | Connection Maintenance | Obtain rolling refresh tokens for scheduled background runs |
3. Implemented Make Modules
Detailed technical specification of each module included in the ChatCoat Make Custom App.
Triggers when a new lead is captured via comments, social campaigns, or inbound webhooks. Emits one bundle per lead record.
Communication Specification
{
"url": "/api/leads",
"method": "GET",
"qs": {
"limit": "{{parameters.limit}}",
"status": "{{parameters.status}}",
"platform": "{{parameters.platform}}"
},
"response": {
"iterate": "{{body}}",
"trigger": {
"type": "date",
"order": "desc",
"id": "{{item.id}}",
"date": "{{item.created_at}}"
},
"output": "{{item}}"
}
}Epoch Specification ("Choose where to start")
Allows users to select starting points in Make ("From now on", "All", or "Choose manually"):
{
"qs": {
"limit": 20
},
"response": {
"iterate": "{{body}}",
"output": {
"label": "{{item.username}} ({{item.platform}})",
"date": "{{item.created_at}}"
}
}
}Creates a lead in the authorized ChatCoat workspace. Returns the full LeadResponse entity.
Communication Specification
{
"url": "/api/leads",
"method": "POST",
"body": {
"platform": "{{parameters.platform}}",
"username": "{{parameters.username}}",
"display_name": "{{parameters.display_name}}",
"source_comment_text": "{{parameters.source_comment_text}}",
"intent": "{{parameters.intent}}",
"status": "{{parameters.status}}",
"tags": "{{parameters.tags}}",
"campaign_id": "{{parameters.campaign_id}}"
},
"response": {
"output": "{{body}}"
}
}Allows Make users to execute arbitrary authenticated requests to any ChatCoat API endpoint (e.g., GET /oauth/me, GET /api/campaigns, or GET /api/analytics/overview) without waiting for a dedicated module.
4. Multi-Tenant Isolation & Security
ChatCoat maintains strict tenant boundary enforcement for all Make operations.
Cryptographically Bound Tokens: Every access token (cca_...) is securely hashed (SHA-256) and bound to the authenticated organization. The backend resolves the workspace directly from the Bearer token—client-side header overrides are never permitted.
User Control & Revocation: Workspace administrators can review, monitor, and revoke active Make connections at any time directly from the ChatCoat web dashboard under Tools → Make (/tools/make).
Make App Directory Review Support
For questions or test account provisioning during the Make partner review process, contact our developer relations team at support@chatcoat.com.