Webhook logo
PDF.co logo

Workflow template

Extract PDF text from a webhook

Extract text from a PDF that PDF.co can access using request.url in webhook JSON. The prepared action uses inline text output and synchronous processing for a small document.

How it works

From an accessible PDF URL to inline text

1 Trigger · 1 Action
Webhook1 · Trigger

Incoming PDF.co request

Receive a nested request object containing url for the PDF. The source must be reachable by PDF.co; this starter does not upload a FastHook File.

PDF.co2 · Action

Extract PDF text from a webhook

Build a PDF-to-text request from request.url with inline fixed to true and async fixed to false. Return the provider's text in the action output; processing consumes PDF.co credits.

The result

Extracted text returned inline by PDF.co

Inspect the actual extraction in the action output. The preview shows the incoming request, not invented document text or a completed provider response.

Example PDF-to-text webhook JSON

{ "request": { "url": "https://pdfco-test-files.s3.us-west-2.amazonaws.com/pdf-to-text/sample.pdf", "inline": true, "async": false } }

Included provider sample URL. inline: true and async: false are enforced by the action mapping, rather than read from the same fields shown in the request example.

Before activation

Set up your workflow

  1. Connect PDF.co and choose a small accessible PDF

    Use your own PDF.co connection and review available credits. Choose a small document PDF.co can retrieve, with permission to send it for processing.

  2. Prepare the nested request object

    Send request.url in webhook JSON. Review the action's inline: true and async: false settings; changing incoming flags does not alter those constants. Protect the webhook before activation.

  3. Inspect the inline extraction

    Activate and submit a controlled PDF URL. Compare the returned text with the document before adding storage or delivery steps. Review processing settings separately if you need to handle larger asynchronous jobs.

Details and limitations
  • The PDF is fetched by URL. The mapping uses request.url, not a top-level url or File field. PDF.co must be able to retrieve the document; browser-session access alone does not establish provider access.

  • Output mode is fixed in the action. inline is true and async is false. Incoming flags do not override them. This starter does not add job-status polling, a completion notification or a document storage destination.

  • Processing uses the connected account's credits. Each request or manual rerun can process the PDF again. Protect the source webhook and review document content, provider limits and allowance before sending larger volumes.

Questions about this template

Where should I put the source PDF URL?

Use request.url inside a nested request object. The PDF must be accessible to PDF.co; the prepared mapping does not upload a FastHook File or read a top-level url field.

Does this return text or a generated PDF?

It requests inline text from PDF-to-text processing. The result remains in the action output; it does not generate another PDF or send the text elsewhere.

Can incoming inline or async flags change processing mode?

No. The action fixes inline to true and async to false. Change the action mapping deliberately and add any needed job handling if you need another processing mode.

Can repeated requests consume more PDF.co credits?

Yes. Requests and manual reruns can process the document again. Review allowance and document suitability, protect the webhook and start with a small controlled PDF.

Explore connected apps

App integrations