Sendblue Tools

Sendblue lets you send and receive iMessage and SMS messages programmatically. Use these tools in a workflow to send an outbound message to a phone number or to pull the list of messages from your Sendblue account.

Overview

Operations

Configuration

sendblue_send_message

Send an iMessage or SMS via Sendblue. Calls POST https://api.sendblue.co/api/send-message.

sendblue_get_messages

Retrieve messages from a Sendblue account. Calls GET https://api.sendblue.co/api/accounts/messages.

Outputs

sendblue_send_message

• data (json) — The Sendblue message object returned by the API.
• metadata (json) — Message metadata.
  • metadata.status (string) — Message status.

sendblue_get_messages

• data (json) — Array of Sendblue message objects.
• metadata (json) — List metadata.
  • metadata.count (number) — Number of messages returned.

YAML Example

sendblue_1:
  type: sendblue
  name: "Sendblue"
  inputs:
    operation: "sendblue_send_message"
    number: "+19998887777"
    content: "Hello from Zelaxy!"
    apiKeyId: "{{SENDBLUE_API_KEY_ID}}"
    apiSecret: "{{SENDBLUE_API_SECRET}}"
  connections:
    outgoing:
      - target: next-block-id

Tips

• Authentication uses two credentials, not one: a Sendblue API key ID (apiKeyId) and a secret (apiSecret). Both are required for every operation and are sent as the sb-api-key-id and sb-api-secret-key headers — store them as environment variables and reference them with {{SENDBLUE_API_KEY_ID}} and {{SENDBLUE_API_SECRET}}.
• For sendblue_send_message, the number must be in E.164 format (leading + and country code, e.g. +19998887777); otherwise Sendblue will reject the request.
• Both number and content have user-or-llm visibility, so they can be supplied by an upstream block (e.g. {{previousBlock.phone}}) or generated by an agent — handy for dynamic outbound messaging.
• The send operation returns the message status under metadata.status; chain a condition block on {{sendblue_1.metadata.status}} to branch on delivery state.