View as Markdown
AlgoDocs icon

AlgoDocs TRIGGER

New Extracted Data

Emit new event for each newly extracted data record for a given AlgoDocs document (polls GET /v1/extracted_data/{documentId}). Each extraction record's stable id is used for deduplication. Run the List Documents action to find a valid document ID before configuring this source. An optional filter narrows emissions to records whose extracted data matches a provided key or value substring. See the documentation.
  • Trigger
  • Polling
  • API key
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's AlgoDocs 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: "algodocs-new-extracted-data",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    algodocs: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    documentId: "Document ID",
  },
  webhookUrl: "https://example.com/webhooks/algodocs",
})

console.log(deployed.id)

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.

New Extracted Data configuration
Property Type Description
timer Polling Interval $.interface.timer
Pipedream will poll the AlgoDocs API on this schedule
Required
documentId Document ID string
The ID of the document. Run the List Documents action to get a list of valid document IDs. Example: 789012.
Required
extractedDataFilter Extracted Data Filter string
Optional. A free-form substring matched client-side against the extracted data of each record; only matching records are emitted. Leave blank to emit every new extraction record. Example: InvoiceNumber or Acme.
Optional

01

Connect

Your user authorizes AlgoDocs 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.

Registry key
algodocs-new-extracted-data
Version
0.0.1
App
AlgoDocs
Authentication
API key
Delivery
Polling source
Output
Events emitted by AlgoDocs.