https://txtfetch.com/integrations/
Wire txtfetch into the platform you already run.
No plugin ships for n8n, Zapier, Make, Airflow, or S3 and Lambda. Each page below shows the platform's own generic HTTP step, wired to the real request and the real fields.
Most of this site assumes you write a request by hand. These five pages don't. They are for a workflow builder, a data engineer, or anyone who wires systems together. These people use a platform's own tools, not a hand-written client.
Every page names the exact generic step the platform already has: an HTTP node, a webhook action, a DAG task, or an event trigger. It also lists the exact fields to set on it. None of these platforms has a dedicated txtfetch app, module, or provider. That is deliberate: the honest answer is a link and a header, not a plugin to install.
Two facts do most of the work on every page. Pass a document's link with the url query parameter. Then the platform never has to forward raw file bytes through an HTTP step built for small JSON payloads. Pass async=true or webhook_url on the same request. Then a slow OCR job never trips the platform's own request timeout.
n8n
One HTTP Request node, a link instead of a file, and an optional webhook for big documents.
explore →
Zapier
Webhooks by Zapier's Custom Request action, a link instead of a file, and a Catch Hook for big jobs.
explore →
Make
The HTTP app's Make a request module, a link instead of a file, and a Webhooks module for big jobs.
explore →
Apache Airflow
A DAG task calling the API directly, a link instead of a file, and a poll-or-webhook path for big batches.
explore →
S3 and Lambda
An S3 object-created event, a presigned URL instead of the raw bytes, and async mode for big uploads.
explore →
Add the step to your automation flow.
One HTTP node with your key does the whole job.
Get an API key →