Make

The BlueBot app for Make (once called Integromat) puts your number into any scenario. It has five instant triggers, eight actions, four searches and Make an API Call for everything else.

The triggers are webhooks: BlueBot posts each event to Make as it happens, so a scenario starts within a second or two and uses no operations on polling. Texts sent from Make go through your sending rules like every other text (pacing, quiet hours, the daily limits, the stop list) and show source: "make" in BlueBot.

Connect your account

To change keys later, open Connections in Make, find the BlueBot connection and press Reauthorize. Every module and webhook that uses the connection follows it.

Instant triggers

Each watch module uses a Make webhook. When you add the module, press Create a webhook, name it and press Save. Make then makes a webhook in your BlueBot account that points at it, subscribed to the events the module needs, and shows it under Developers → Webhooks in BlueBot described as “Make: ” and the webhook’s name. Deleting the webhook in Make deletes it in BlueBot too. A module’s settings (such as the states to watch) are fixed when the webhook is made; to change them, make a new webhook.

When the scenario is off, Make keeps what arrives in the webhook’s queue and works through it when you turn the scenario back on. BlueBot also retries a delivery Make doesn’t accept for about three days, with each event’s id the same on every try.

Each bundle is the record as the API returns it (a message, a contact or an enrollment), plus event_id, event_type and event_timestamp. A text’s files are an array; put an Iterator after the trigger to handle each picture on its own.

Watch Incoming Texts

Starts when somebody texts your number. BlueBot sends it message.received.

BlueBot copies the texts of people you’ve texted through it, unless you set Which chats to copy to Everything in Settings → Sending rules.

Watch Text Status Changes

Starts when a text you sent changes state.

The bundle is the message after the change, with state, failure and metadata. Delivered and read come only from iMessage, and read only from people who share read receipts.

Watch New Contacts

Starts when a person is added to your contacts, however they were added. BlueBot sends it contact.created. Its only field is the webhook.

Watch Contact Stops

Starts when somebody goes on your stop list. Their queued texts are already canceled. BlueBot sends it contact.stopped.

Watch Completed Sequences

Starts when a person reaches the end of a sequence or leaves it early. BlueBot sends it sequence.completed.

The bundle is the enrollment (id, sequence_id, contact_id, state, stop_reason, completed_at) with contact_handle, contact_first_name and contact_last_name.

Actions

Every action that sends a text carries an Idempotency-Key unique to that run of that module. If Make runs the module again in the same execution (a Break error handler retrying it, say), BlueBot answers with the text it already accepted instead of sending a second one.

Send Text

Sends a text from your number now, or as soon as your sending rules allow. The output bundle is the message, usually state: "queued".

A held text (quiet hours, your Mac offline, a daily limit) still succeeds, with hold.reason and hold.until in the bundle. A text to somebody on your stop list succeeds with state: "canceled" and cancel_reason: "opted_out"; add a filter on State if later modules should only run for texts that will go.

Send Template

The bundle is the message, with the template’s words filled in as text. A variable with no value and no fallback fails the module with invalid_request and the variable’s name, and nothing is sent.

Schedule Text

The fields of Send Text plus Send at (Date, required). The text waits as scheduled until then, then goes through your sending rules, so one due inside quiet hours goes in the morning. Files are uploaded when the module runs, and an unsent file is deleted after a day, so schedule texts with files at most a day ahead. Keep the output’s id to cancel it later.

Cancel Scheduled Text

The bundle is the message with state: "canceled". A text the Mac already took can’t be called back, and the module fails with conflict.

Create or Update Contact

An empty field doesn’t clear what BlueBot has. The bundle is the contact, with created: true when they were new.

Add Tag

Enroll in Sequence

Somebody already in the sequence, or on your stop list, isn’t started, and the module fails with conflict. Add an Ignore error handler to the module if the scenario should carry on.

Remove from Sequence

Their texts from it that haven’t gone are canceled. The bundle’s enrollments lists the enrollment that ended, or nothing when they weren’t in the sequence, which isn’t an error. To take somebody off every sequence, add a module for each one.

Searches

Search Messages

Lists texts, newest first, one bundle each. It calls GET /v1/messages and follows the cursor for you.

Find Contact

Returns one bundle for the contact, or none. Add a router with Create or Update Contact on the empty path to add people you don’t have.

Find Conversation

Returns one bundle, or none when you’ve never texted them: conversation_id, contact_id, last_message_id, last_message_text, last_message_direction, last_message_state, last_message_at and waiting_on_you (true when the newest text came from them). Texts in a group chat they’re in, and texts of yours that never went, don’t count.

Check iMessage

Calls GET /v1/lookup, which reads your own Messages history through your Mac and waits up to 15 seconds. Returns service (imessage, sms or unknown), basis and last_seen_at. A number you’ve never texted is unknown: Apple gives no way to ask. You don’t need it before sending, since Service: Auto tries iMessage first.

Make an API Call

Calls any endpoint in the API with your connection’s key.

The bundle is the status code, the headers and the body. A list answers one page; read next_cursor and call again with it as cursor for the next.

When a module fails

The app turns BlueBot’s error into Make’s, with BlueBot’s message, its hint, the code and the request id. Quote the request id if you write to support.

A held text is not an error, and neither is a text that fails after it was accepted: catch those with Watch Text Status Changes.

Test a scenario

The recipes show the fields to map for many apps, and Webhooks explains what BlueBot sends.