# New Extracted Data — AlgoDocs

> 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…

- Key: `algodocs-new-extracted-data`
- Type: Trigger (Polling)
- Version: 0.0.1
- App: AlgoDocs (`algodocs`) — https://pipedream.com/apps/algodocs.md
- This page (HTML): https://pipedream.com/apps/algodocs/triggers/new-extracted-data
- Source: https://github.com/PipedreamHQ/pipedream/blob/master/components/algodocs/sources/new-extracted-data/new-extracted-data.mjs

## Description

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](https://api.algodocs.com/).

## Props

| Prop | Type | Required | Description |
|---|---|---|---|
| `timer` | `$.interface.timer` | Yes | Pipedream will poll the AlgoDocs API on this schedule |
| `documentId` | `string` | Yes | The ID of the document. Run the List Documents action to get a list of valid document IDs. Example: 789012. |
| `extractedDataFilter` | `string` | No | 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. |

## Returns

Events emitted by AlgoDocs.

## Run it

**TypeScript**

```ts
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)
```

**cURL**

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

**MCP**

MCP servers expose AlgoDocs actions as on-demand tools.

New Extracted Data 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.

## Event delivery

Every event is sent to the HTTP endpoint you choose when you deploy the source. Or: no webhook required — your app or agent can fetch recent events from the [trigger events API](https://pipedream.com/docs/connect/api-reference/list-trigger-events.md) instead.

---

- App: https://pipedream.com/apps/algodocs.md · All apps: https://pipedream.com/apps