Intercom TRIGGER
New Topic (Instant)
- Trigger
- Instant
- OAuth
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's Intercom account, configure the source, and choose the webhook where your backend receives events.
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 deployed = await pd.triggers.deploy({
id: "intercom-new-topic",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
intercom: { authProvisionId: "apn_xxxxxxx" },
clientSecret: "Client Secret",
},
webhookUrl: "https://example.com/webhooks/intercom",
})
console.log(deployed.id)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/triggers/deploy \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "intercom-new-topic",
"webhook_url": "https://example.com/webhooks/intercom",
"configured_props": {
"intercom": { "authProvisionId": "apn_xxxxxxx" },
"clientSecret": "Client Secret"
}
}'MCP servers expose Intercom actions as on-demand tools.
New Topic (Instant) is an event source, so your application deploys it
with the Connect SDK or API and then either receives each event at a
webhook URL or retrieves events on demand with the trigger events API.MCP exposes on-demand actions. Event sources are deployed through the Connect SDK or API because they continue listening after the initial request.
SCHEMA
Configuration
These inputs define which events the source watches. Dynamic options are loaded from the connected account.
| Property | Type | Description |
|---|---|---|
clientSecret Client Secret | string | Highly recommended. The client secret for your Intercom app. The client secret can be found in your app basic information page. See more here. Optional |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes Intercom through Pipedream managed auth.
02
Deploy
Your backend deploys this source with that user's own configuration.
03
Webhook delivery
Every event is sent to the HTTP endpoint you choose when you deploy the source — as it happens.
OR
On-demand retrieval
No webhook required. Your app or agent can fetch recent events from the trigger events API.
REFERENCE
Trigger details
- Registry key
- intercom-new-topic
- Version
- 0.0.6
- App
- Intercom
- Authentication
- OAuth
- Delivery
- Instant event
- Output
- Events emitted by Intercom.
- Source
- View on GitHub ↗