Skip to content
Project Blue Support Docs home
InboxAsk a human

Managing Automations & STOP Replies on API-Only Integrations

If you're running your own send timing and workflow logic outside Project Blue, this article covers what (if anything) can send on our side, and how opt-outs work.

Does Project Blue send anything on its own?

Not by default. Project Blue doesn't have a background process that sends messages unless one of the following has been explicitly set up on your account:

  • Project Blue native workflows — automations you (or a teammate) built in the Project Blue portal.

  • CRM-side workflows — if you have a CRM connected (GoHighLevel, HubSpot, Close), any workflow there that uses a Project Blue send action.

If your integration is API-only with no Project Blue workflows and no connected CRM automations, nothing sends without your API call triggering it.

Turning off existing automations

There isn't a single global "pause all sending" switch — automations are turned off the same way they were turned on:

  1. In the Project Blue portal, check Automations for any native workflows and pause or delete the ones you don't want running.

  2. If a CRM is connected, check that CRM's own workflow builder for any steps using a Project Blue send action, and pause those workflows there.

If you're not sure whether your account has any native workflows or a connected CRM with automations, reach out to support and we'll confirm what's active on your account before you go live.

Handling STOP replies

Project Blue does not automatically detect or block STOP replies, and there is no built-in suppression list on the API today. A STOP reply arrives as a normal inbound webhook/message like any other — it's on you to detect it and act on it.

Recommended approach for API-only integrations:

  • Check the body of every inbound message for opt-out keywords (STOP, UNSUBSCRIBE, etc.).

  • When detected, mark that contact as opted out in your own system and suppress future automated sends to them.

  • If you also have CRM workflows running alongside the API, make sure those workflows independently check opt-out/DND status before sending — a contact being opted out on your side doesn't automatically stop a separate CRM workflow.

For general compliance guidance: for transactional (non-marketing) messages, best practice is to only message people with an existing relationship to your business, keep content informational, honor STOP promptly, and identify your business in the conversation. This isn't legal advice — consult your own counsel for TCPA/compliance requirements specific to your use case.