Brilliant Directories ACTION
Create Post
Creates a single or group post. See the documentation
- Action
- Writes data
- Destructive
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Brilliant Directories account once, then configure and run Create 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: "brilliant_directories-create-post",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
brilliant_directories: { authProvisionId: "apn_xxxxxxx" },
userId: 10,
dataId: 10,
},
})
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": "brilliant_directories-create-post",
"configured_props": {
"brilliant_directories": { "authProvisionId": "apn_xxxxxxx" },
"userId": 10,
"dataId": 10
}
}'// 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": "brilliant_directories",
},
},
},
)
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: "brilliant_directories-create-post",
arguments: {
userId: 10,
dataId: 10,
},
})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 |
|---|---|---|
userId User ID | integer | The unique identifier for a user. Required |
dataId Data ID | integer | The data id for the post. Required |
dataType Data Type | integer | The data type for the post. Required |
postTitle Post Title | string | The title of the post. Required |
postContent Post Content | string | The content of the post. Optional |
postCategory Post Category | string | The category of the post. Optional |
postType Post Type | string | The type of the post. Optional |
postTags Post Tags | string[] | A list of tags to the post. Optional |
postStatus Post Status | boolean | The status of the post. Optional |
postStartDate Post Start Date | string | The start date of the post. Format yyyymmddhhmmss 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
- brilliant_directories-create-post
- Version
- 0.0.2
- App
- Brilliant Directories
- Authentication
- API key
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗