Envoy ACTION
Create an Invite
Create an Invite to a person to visit a location. See the docs.
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Envoy account once, then configure and run Create an Invite 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: "envoy-create-an-invite",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
envoy: { authProvisionId: "apn_xxxxxxx" },
expectedArrivalAt: "Arrival date",
locationId: "Location",
},
})
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": "envoy-create-an-invite",
"configured_props": {
"envoy": { "authProvisionId": "apn_xxxxxxx" },
"expectedArrivalAt": "Arrival date",
"locationId": "Location"
}
}'// 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": "envoy",
},
},
},
)
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: "envoy-create-an-invite",
arguments: {
expectedArrivalAt: "Arrival date",
locationId: "Location",
},
})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 |
|---|---|---|
expectedArrivalAt Arrival date | string | A date-time string at UTC, such as 2007-12-03T10:15:30Z, compliant with the date-time format outlined in section 5.6 of the RFC 3339 profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar. Required |
locationId Location | string | Unique identifier of a location. Required Dynamic |
name Name | string | Visitor full name. Required |
email Email | string | Visitor email address. Optional |
hostEmployeeId Host | string | Unique identifier of a host. Optional Dynamic |
expectedDepartureAt Departure date | string | A date-time string at UTC, such as 2007-12-03T10:15:30Z, compliant with the date-time format outlined in section 5.6 of the RFC 3339 profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar. Optional |
notes Private notes | string | Enter your private notes. Optional |
sendEmailToInvitee Send email to invitee | boolean | Either it should or not send email to invitee 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
- envoy-create-an-invite
- Version
- 0.0.2
- App
- Envoy
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗