Intuiface ACTION
Send Message
Send messages to any connected Intuiface Player running an experience that embeds the Web Triggers Interface Asset. See the docs.
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Intuiface account once, then configure and run Send 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: "intuiface-send-message",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
intuiface: { authProvisionId: "apn_xxxxxxx" },
message: "Message",
parameter1: "Parameter 1",
},
})
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": "intuiface-send-message",
"configured_props": {
"intuiface": { "authProvisionId": "apn_xxxxxxx" },
"message": "Message",
"parameter1": "Parameter 1"
}
}'// 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": "intuiface",
},
},
},
)
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: "intuiface-send-message",
arguments: {
message: "Message",
parameter1: "Parameter 1",
},
})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 |
|---|---|---|
message Message | string | Value to send to all experiences satisfying any filter(s) specified below. If no filters are applied then all accessible experiences will be targeted. Required |
parameter1 Parameter 1 | string | An additional value that can be sent to all selected experiences. Optional |
parameter2 Parameter 2 | string | An additional value that can be sent to all selected experiences. Optional |
parameter3 Parameter 3 | string | An additional value that can be sent to all selected experiences. Optional |
experienceNames Experience Names | string[] | Specify experience(s) based on their name(s). Optional Dynamic |
experienceIds Experience IDs | string[] | Specify experience(s) based on their ID(s). Optional Dynamic |
playerDeviceNames Player Device Names | string[] | Specify player(s) based on their device name(s). Optional Dynamic |
playerIds Player IDs | string[] | Specify player(s) based on their device ID(s). Optional Dynamic |
playerTags Player Tags | string[] | Specify player(s) based on their tag(s). 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
- intuiface-send-message
- Version
- 0.0.3
- App
- Intuiface
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗