Build it
What do you want Parseur and Workflowy 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 Parseur and Workflowy
Triggers and actions 6 triggers · 20 actions
Trigger
New Document Export FailedTriggered when Parseur fails to export a document to its destination.
Trigger
New Document Not ProcessedTriggered when Parseur receives a document it cannot extract data from, so you can follow it up.
Trigger
New Document ProcessedTriggered when Parseur finishes extracting data from a document, with the extracted fields.
Trigger
New Document Processed (With List Items)Triggered when Parseur finishes extracting data from a document, including any table or list fields it found (line items, rows).
Trigger
New MailboxTriggers when a new mailbox is created in your Parseur account. Returns the mailbox's name, email prefix, AI engine and document counts.
Trigger
New Table Field ProcessedTriggers once for every row of a table or list field when Parseur finishes processing a document. Returns the row's values along with the document and mailbox it came from.
Action
Create DocumentSends text or HTML content to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.
Action
Create Document From FileUploads a file (PDF, DOCX, image and so on) to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.
Action
Delete DocumentDeletes a document from Parseur by its ID.
Action
Delete MailboxDeletes a Parseur mailbox and everything in it. This cannot be undone.
Action
Get DocumentReturns one document from Parseur by its ID, including its processing status and the data Parseur extracted from it.
Action
Get MailboxReturns one Parseur mailbox by its ID, with its email address, document counts and settings.
Action
List DocumentsReturns the documents in Parseur, optionally narrowed to one mailbox or one processing status.
Action
List MailboxesReturns the mailboxes in your Parseur account, with the email address to send documents to and how many documents each holds.
Action
Reprocess DocumentSends an existing document back through parsing, for example after you update its template. Returns the document's ID, name and processing status.
Action
Update MailboxUpdates a Parseur mailbox's settings. Only the values you supply are changed — anything you leave blank keeps its current setting.
Action
Complete a bulletMarks an existing Workflowy bullet as complete. Give it the bullet's ID; Workflowy checks the bullet off in place.
Action
Create BulletCreates a new bullet in Workflowy, optionally under a parent bullet, with its text, note, layout and position.
Action
Delete a bulletDeletes a bullet from Workflowy by its ID, along with anything nested under it.
Action
Export all bulletsReturns the entire Workflowy outline for the account — every bullet with its text, note and nested children. Workflowy allows one export per minute.
Action
Get a bulletReturns one Workflowy bullet by its ID, including its text, note, parent, completion state and timestamps.
Action
List bulletsLists Workflowy bullets — the children of a given bullet, or the top-level bullets when no parent is given.
Action
List targetsLists the saved target locations in Workflowy — the places this connection is allowed to add bullets to.
Action
Move a bulletMoves a Workflowy bullet under a different parent bullet, optionally at a specific position among its new siblings.
Action
Uncomplete a bulletUn-checks a completed Workflowy bullet, putting it back to not-done.
Action
Update a bulletUpdates an existing Workflowy bullet's text, note or layout. Anything left blank is left as it is.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.