View as Markdown
Sendblue icon

Sendblue TRIGGER

New Message Received

Emit new event when a new inbound message is received. See the documentation
  • Trigger
  • Polling
  • API key
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's Sendblue account, configure the source, and choose the webhook where your backend receives events.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const deployed = await pd.triggers.deploy({
  id: "sendblue-new-message-received",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    sendblue: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    accountEmail: "Account Email",
  },
  webhookUrl: "https://example.com/webhooks/sendblue",
})

console.log(deployed.id)

MCP exposes on-demand actions. Event sources are deployed through the Connect SDK or API because they continue listening after the initial request.

SCHEMA

Configuration

These inputs define which events the source watches. Dynamic options are loaded from the connected account.

New Message Received configuration
Property Type Description
timer Timer $.interface.timer
Required
accountEmail Account Email string
Filter by account email
Optional
fromNumberFilter From Number string
Filter by sender phone number
Optional
toNumberFilter To Number string
Filter by recipient phone number
Optional
groupIdFilter Group ID string
Filter by group ID
Optional
messageTypeFilter Message Type string
Filter by message type
Optional
serviceFilter Service Type string
Filter by service type
Optional
statusFilter Status string
Filter by message status
Optional
orderBy Order By string
Field to order messages by
Optional
orderDirection Order Direction string
Sort order
Optional
limit Limit integer
Maximum number of messages to return (1-1000)
Optional

01

Connect

Your user authorizes Sendblue through Pipedream managed auth.

02

Deploy

Your backend deploys this source with that user's own configuration.

03

Webhook delivery

Every event is sent to the HTTP endpoint you choose when you deploy the source — after each poll.

OR

On-demand retrieval

No webhook required. Your app or agent can fetch recent events from the trigger events API.

Registry key
sendblue-new-message-received
Version
0.0.1
App
Sendblue
Authentication
API key
Delivery
Polling source
Output
Events emitted by Sendblue.