Intercom ACTION
Send Message To Contact
Sends an outbound message from an admin to a contact in Intercom (POST /messages). Set Message Type to
in_app for an in-app message or email for an email — email messages require Subject and support Template (plain or personal). Use List Admin ID Options to find a valid From ID and Search Contacts to find a valid To ID. Example: set Message Type to email, Subject to Welcome!, Template to personal, From ID to 25, To Type to user, and To ID to 536e564f316c83104c000020 to send a personal welcome email to that contact. See the documentation.- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Intercom account once, then configure and run Send Message To Contact from your backend or agent.
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 result = await pd.actions.run({
id: "intercom-send-message-to-contact",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
intercom: { authProvisionId: "apn_xxxxxxx" },
messageType: "Message Type",
subject: "Subject",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "intercom-send-message-to-contact",
"configured_props": {
"intercom": { "authProvisionId": "apn_xxxxxxx" },
"messageType": "Message Type",
"subject": "Subject"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "intercom",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "intercom-send-message-to-contact",
arguments: {
messageType: "Message Type",
subject: "Subject",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
messageType Message Type | string | The kind of message being created. Required |
subject Subject | string | The title of the email. Required |
body Body | string | The content of the message. HTML and plaintext are supported. Required |
template Template | string | The style of the outgoing message. Required |
fromId From ID | string | The sender of the message. The identifier for the admin which is given by Intercom. If not provided, the default sender will be used. Required |
toType To Type | string | The type of the recipient of the message. Required |
toId To ID | string | The recipient of the message. The identifier for the contact which is given by Intercom. Eg. 536e564f316c83104c000020. Required |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- intercom-send-message-to-contact
- Version
- 0.0.5
- App
- Intercom
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗