letmepost ACTION
Publish a Post
Publish or schedule a post to one or more connected accounts. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's letmepost account once, then configure and run Publish a Post 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: "letmepost-publish-post",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
letmepost: { authProvisionId: "apn_xxxxxxx" },
accounts: ["Accounts"],
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": "letmepost-publish-post",
"configured_props": {
"letmepost": { "authProvisionId": "apn_xxxxxxx" },
"accounts": ["Accounts"],
"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": "letmepost",
},
},
},
)
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: "letmepost-publish-post",
arguments: {
accounts: ["Accounts"],
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 |
|---|---|---|
accounts Accounts | string[] | The connected accounts to publish to. List Accounts action can be used to discover account IDs. Required Dynamic |
text Text | string | The post body. Optional when the post is media-only on platforms that allow it. Optional |
media Media | string[] | Media attachments. Each item is a JSON object with kind (image or video) and exactly one of url or mediaId, plus an optional altText. Example: {"kind":"image","url":"https://cdn.example.com/launch.jpg","altText":"Launch banner"} Optional |
firstComment First Comment | string | Posted as the first comment under the published post, where the platform supports it. Optional |
publishNow Publish Now | boolean | Publish immediately. Turn off to schedule for a future time. Optional |
scheduledAt Schedule At | string | When to publish the post (ISO 8601). Required when Publish Now is off. Optional |
profileId Profile ID | string | UUID of a letmepost profile. Example: 550e8400-e29b-41d4-a716-446655440000. Discover valid values from the profileId field on posts returned by List Posts or Get Post. Optional |
idempotencyKey Idempotency Key | string | Reusing the same key never publishes twice, which makes retries safe. 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
- letmepost-publish-post
- Version
- 0.0.2
- App
- letmepost
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗