LoopMessage ACTION
Send Outbound Message
Action to send a message to an individual recipient.
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's LoopMessage account once, then configure and run Send Outbound Message 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: "loopmessage-send-text-message",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
loopmessage: { authProvisionId: "apn_xxxxxxx" },
contact: "Contact",
text: "Text",
},
})
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": "loopmessage-send-text-message",
"configured_props": {
"loopmessage": { "authProvisionId": "apn_xxxxxxx" },
"contact": "Contact",
"text": "Text"
}
}'// 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": "loopmessage",
},
},
},
)
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: "loopmessage-send-text-message",
arguments: {
contact: "Contact",
text: "Text",
},
})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 |
|---|---|---|
contact Contact | string | Recipient phone number or email address. Required |
text Text | string | Message text. Required |
subject Subject | string | Optional. Message subject. A recipient will see this subject as a bold title before the text. For iMessage only. Optional |
effect Effect | string | Optional. Add effect to your message. For iMessage only. Optional |
sender Sender | string | Optional. Use a specific Sender Name for outbound message. Optional Dynamic |
attachments Attachments | string[] | Optional. An array of strings. The string must be a full URL of your image. URL should start with https://. HTTP links (without SSL) are not supported. This must be a publicly accessible file URL: we will not be able to reach any URLs that are hidden or that require authentication. Optional |
replyToId Reply To ID | string | Optional. Reply to a message with a specific ID Optional |
channel Channel | string | Optional. You can choose which service to use to deliver the message. By default, the required channel will be determined automatically.
Use this parameter only in cases when you need to override the delivery channel for a specific request. DON'T use it as a default parameter for all requests. Optional |
passthrough Passthrough | string | Optional. A string of metadata you wish to store in this request. Max length: 1000 characters. Optional |
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
- loopmessage-send-text-message
- Version
- 0.0.4
- App
- LoopMessage
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗