AlgoDocs TRIGGER

New Table Row Extracted

Emit new event for each individual table row extracted from an AlgoDocs document (polls GET /v1/extracted_data/{documentId}). AlgoDocs represents a record's extracted data as a flat object, with any table/repeating field appearing as an array-valued property (e.g. data.LineItems). Unlike New Extracted Data which emits one event per extraction record, this source emits one event per row within each such array field; records with no array-valued field in data produce no events. Requires a document ID — run List Documents to find one. An optional filter narrows emissions to rows whose JSON representation contains a specified substring. See the documentation.

Trigger
Polling
API key
Webhook delivery

Start building

IMPLEMENTATION

Deploy this event source

Connect the user's AlgoDocs account, configure the source, and choose the webhook where your backend receives events.

Pipedream Connect

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-table-row-extracted",
  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)

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": "algodocs-new-table-row-extracted",
    "webhook_url": "https://example.com/webhooks/algodocs",
    "configured_props": {
      "algodocs": { "authProvisionId": "apn_xxxxxxx" },
      "timer": { "intervalSeconds": 900 },
      "documentId": "Document ID"
    }
  }'

MCP servers expose AlgoDocs actions as on-demand tools.

New Table Row Extracted 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.

New Table Row Extracted 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
`tableRowFilter` Table Row Filter	`string`	Optional. A free-form substring matched client-side against the JSON representation of each extracted table row; only rows whose JSON contains this substring are emitted. Leave blank to emit every row. Example: `InvoiceNumber` or `Acme`. Optional

LIFECYCLE

Event delivery

Connect

Your user authorizes AlgoDocs through Pipedream managed auth.

Deploy

Your backend deploys this source with that user's own configuration.

Webhook delivery

Every event is sent to the HTTP endpoint you choose when you deploy the source — after each poll.

On-demand retrieval

No webhook required. Your app or agent can fetch recent events from the trigger events API.

REFERENCE

Trigger details

Registry key: algodocs-new-table-row-extracted
Version: 0.0.1
App: AlgoDocs
Authentication: API key
Delivery: Polling source
Output: Events emitted by AlgoDocs.
Source: View on GitHub ↗

Deploy this event source #

Configuration #

Event delivery #