Integration
Connect Docparser to Cloudflare Trace
When something happens in Docparser, your agent does the next thing in Cloudflare Trace. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Docparser and Cloudflare Trace to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Docparser and Cloudflare Trace
Triggers and actions 2 triggers · 4 actions
Trigger
Parsed Document Data AvailableTriggers whenever a new Document is processed and parsed data is available.
- Parsed Table Row Available
Triggers whenever a new Document is processed and parsed table rows are available.
- Fetch Document From URL
Fetches a new document from a publicly accessible URL and imports it into Docparser to begin parsing. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).
- Upload Document
Uploads a new document to Docparser which will immediately begin parsing after reception. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).
Action
Get geolocation infoLook up the geolocation Cloudflare reports for this automation's own outbound requests — city, region, country, postal code, latitude and longitude — plus the IP address, network operator (ASN) and the Cloudflare data center serving it, from Cloudflare's speed-test metadata endpoint. Takes no input.
- Get trace info
Fetch the requester's IP address, timestamp, user agent, country code, TLS/HTTP version, and other network metadata from Cloudflare's trace endpoint.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.