[API & integrations](https://missblue.dev/help/collections/api-and-integrations) # Connect messaging to your CRM Choose the right project, test the event flow, and coordinate automation with your team. Miss Blue team Updated September 14, 2026 2 min read [Browse this collection](https://missblue.dev/help/collections/api-and-integrations) ## Decide what the integration should do Start with one complete workflow: a new inquiry creates an expected message, the recipient replies, and the reply reaches the correct CRM record and team. Decide who owns the next response when a person replies. Choose the intended Miss Blue organization, project, and sending number before configuring credentials. Use the supported integration for your CRM when one is available, or connect through the public API and webhooks. - [GoHighLevel integration guide](https://missblue.dev/docs/gohighlevel) - [API documentation](https://missblue.dev/docs) ## Keep credentials on your server Store API keys in your integration’s secret configuration. Do not put them in a browser widget, a public repository, screenshots, or support messages. Give the integration access to the intended sending numbers and check that an unavailable number produces a clear error. If you need to troubleshoot with support, share a request ID, approximate time and timezone, and the error code. Those details are useful without exposing the credential. ## Test the whole event flow 1. Use a sandbox key to create a simulated message from your workflow. 2. Record the returned message and conversation identifiers alongside your CRM record. 3. Test delivery updates and an inbound reply through your registered test webhook. 4. Verify that repeated webhook events do not create duplicate activities or trigger repeated replies. 5. Test failed, rate-limited, and timed-out requests before switching to a live key and a consenting test recipient. - [Webhook and inbound-message guide](https://missblue.dev/docs/receiving-messages) - [Start with the sandbox](https://missblue.dev/help/articles/test-with-the-sandbox) ## Keep automation and people in sync - Pause automated follow-ups when a member takes over the conversation. - Prevent your integration from treating its own outbound activity as a new inbound reply. - Update the external CRM or sequence when a person asks you to stop. A Miss Blue block does not edit the CRM’s preferences. - Keep a clear route for a person to review errors or unusual replies. - Check that the workflow still uses the intended project and number after changing team access. ## Related articles - [Connect GoHighLevel with Beta access Request Beta access, connect a sub-account, and verify direct messages and media in both inboxes. 2 min read](https://missblue.dev/help/articles/connect-gohighlevel) - [Create, rotate, and revoke an API key Choose live or sandbox mode, show or copy a key again when you need it, and replace a credential without losing track of its use. 2 min read](https://missblue.dev/help/articles/create-and-rotate-api-keys) - [Set up webhooks for replies and delivery events Choose events, store the signing secret, and diagnose a receiver that is not accepting deliveries. 3 min read](https://missblue.dev/help/articles/set-up-webhooks) ## Still need a hand? Send us your question, or text the team at (929) 272-7048. [Contact the team](https://missblue.dev/contact) [Text us](sms:+19292727048)