Insites TRIGGER
New Analysis Complete
- Trigger
- Polling
- API key
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's Insites 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: "insites-analysis-complete",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
insites: { authProvisionId: "apn_xxxxxxx" },
timer: { "intervalSeconds": 900 },
filter: "Filter",
},
webhookUrl: "https://example.com/webhooks/insites",
})
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": "insites-analysis-complete",
"webhook_url": "https://example.com/webhooks/insites",
"configured_props": {
"insites": { "authProvisionId": "apn_xxxxxxx" },
"timer": { "intervalSeconds": 900 },
"filter": "Filter"
}
}'MCP servers expose Insites actions as on-demand tools.
New Analysis Complete 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 |
|---|---|---|
timer Timer | $.interface.timer | Required |
filter Filter | string | JSON encoded string - attributes by which the reports should be filtered by. See the documentation for more details. Example: [{"operator":"equal","property":"mobile.is_mobile","targetValue":false}] Optional |
includeHistoric Include Historic | boolean | Whether the results should contain old versions of the business reports. Optional |
listId List ID | string | Will filter the results and return only those in the given list. Note: list ID should be the 32-character hexadecimal ID provided by Insites (not the list name which is assigned by the user). Optional |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes Insites 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 — after each poll.
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
- insites-analysis-complete
- Version
- 0.0.2
- App
- Insites
- Authentication
- API key
- Delivery
- Polling source
- Output
- Events emitted by Insites.
- Source
- View on GitHub ↗