Affinda TRIGGER
New Document Parse Completed
- Trigger
- Instant
- API key
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's Affinda 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: "affinda-document-parse-completed",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
affinda: { authProvisionId: "apn_xxxxxxx" },
organization: "Organization",
webhookSignatureKey: "Webhook Signature Key",
},
webhookUrl: "https://example.com/webhooks/affinda",
})
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": "affinda-document-parse-completed",
"webhook_url": "https://example.com/webhooks/affinda",
"configured_props": {
"affinda": { "authProvisionId": "apn_xxxxxxx" },
"organization": "Organization",
"webhookSignatureKey": "Webhook Signature Key"
}
}'MCP servers expose Affinda actions as on-demand tools.
New Document Parse Completed 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 |
|---|---|---|
organization Organization | string | The organization Required Dynamic |
webhookSignatureKey Webhook Signature Key | string | If provided, this source will verify if the webhook comes from Affinda. Locate it in your organization settings. Optional |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes Affinda 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
- affinda-document-parse-completed
- Version
- 0.0.1
- App
- Affinda
- Authentication
- API key
- Delivery
- Instant event
- Output
- Events emitted by Affinda.
- Source
- View on GitHub ↗