Reading, recording and sending messages are different API operations. Select the endpoint that matches the authorized behavior.

Before you beginConfirm the business, contact, channel setup, scopes and permission to contact the recipient.

Step by step

  1. Read the current conversation and message contracts; distinguish retrieval, inbound recording and outbound send operations.
  2. Resolve the authorized conversation or contact ID and verify its account context.
  3. For reads, implement the documented pagination and retrieve only data needed by the integration.
  4. For an approved send, validate recipient, supported channel, attachments and communication preferences before submission.
  5. Use a controlled recipient to test the result. Keep accepted, delivered and failed states separate.
  6. Correlate safe message identifiers and avoid automatic resend after an uncertain response. Check the original message first.

Expected result

The integration performs the intended message operation once and reports its observed status.

Troubleshooting

  • An inbound-record endpoint is not a substitute for sending a customer message.
  • A conversation ID from a different business must not be reused.
  • Do not log full message bodies or credentials by default.

Supporting documentation

These links open the provider’s documentation. Availability and permissions depend on your account.

More guides

Start a scoped CentriCRM integrationSelect authentication, verify account context and scopes, and plan webhook handling before enabling writes.
Synchronize contacts without replacing unrelated dataUse account identity, duplicate policy and narrow updates deliberately.
Read calendar availability safelyKeep calendar identity, range and timezone explicit.
Map opportunity state between systemsUse explicit pipeline and stage mappings before synchronizing deals.