CRM and phone-system integrations
Three integration patterns:
1. Native webhooks (recommended)
For any CRM that speaks webhooks (HubSpot, Pipedrive, Zoho, GoHighLevel, Attio, Close, etc).
- CRM: configure an inbound webhook endpoint.
- SMSGate → webhooks → add the URL, format Native, pick events.
- Verify
x-smsgw-signature(HMAC-SHA256 of body with webhook secret).
2. Twilio-compatible
Already have Twilio-based code? Change the base URL.
curl -u any:sk_your_key \
https://sms.001.com.mx/api/v1/twilio/2010-04-01/Accounts/any/Messages.json \
--data-urlencode "To=+15551234567" \
--data-urlencode "Body=hi"
For Twilio-shaped webhooks to your CRM: in SMSGate → webhooks, pick format Twilio-compatible. You’ll get form-encoded From/To/Body/MessageSid/MessageStatus/NumMedia/MediaUrl0..N.
3. 3CX (Generic SMS Provider)
3CX Admin → SMS → Providers → add a Generic Provider:
- Send URL:
https://sms.001.com.mx/api/v1/3cx/send - Auth: HTTP Basic. Username = anything. Password = your API key.
- Test URL:
https://sms.001.com.mx/api/v1/3cx/health
For inbound to 3CX, add a webhook pointed at 3CX’s receive URL with format 3CX.
4. Zapier / Make / n8n
Universal no-code adapter:
- Trigger: Catch Hook → your SMSGate webhook URL.
- Action: HTTP POST →
https://sms.001.com.mx/api/v1/sendwith Bearer token.
This opens 5,000+ apps.
Mapping table
| CRM | Inbound lands in | Send via |
|---|---|---|
| HubSpot | Timeline / Note | Workflow “Send SMS” |
| Pipedrive | Activity (SMS type) | Webhook via Zapier |
| Zoho CRM | Activities | Function + REST |
| 3CX | Internal chat | Generic SMS Provider |
| GoHighLevel | Conversations | Native webhook |