BookFunnel
CMS & ContentConnect AI agents to BookFunnel, which delivers ebooks and audiobooks to readers for authors and publishers. Agents queue download links to buyers and read the books and account records behind each send, though no action confirms a link was received.
What This Integration Enables
BookFunnel is the delivery layer, not the storefront. Something else records the sale, the mailing list signup, or the giveaway entry, and BookFunnel is what actually puts the file in the reader's hands. That division is why this connector belongs at the end of a flow rather than the start of one: agents generate a per reader download link against a single book with Create Book Download Link or against an opt in landing page with Create Page Download Link, hand BookFunnel the sending job with Email Download Link, or grant library access with no email at all through Add Book To Library. List Books is the only way to discover the Book UID that every delivery action needs, and Test Access confirms which BookFunnel account a connection is pointed at before anything ships.
Three properties should shape how you design around it. BookFunnel has no triggers. It publishes no webhook subscription API and no event payload shape, so nothing here listens and FlowRunner receives no events from BookFunnel. Flows start from the system that actually knows a delivery is owed: a paid order from the storefront, a new subscriber event from the email platform, a form submission, or a schedule that sweeps a list and reads List Books when it gets there. Second, every delivery action is permanent. BookFunnel documents no operation to remove a book from a reader's library, revoke a generated link, or delete a row from a landing page's CSV export, so an agent working here is writing in ink. Third, the connector does not confirm delivery. Email Download Link reports that the email was queued and returns the link and code alongside that, which is a different fact from the reader receiving it. Refresh Access Token and Revoke Access Token exist to rotate the OAuth2 credential the connection itself uses, and are not a way to gate or expire reader access. Agents that can act without a human are exactly the agents that need a place to stop, and on a platform with no undo, that place is before the send.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Storefront Order Fulfillment
A buyer completes a purchase for a digital title in Shopify, WooCommerce, or Gumroad. The agent reads the paid order, resolves the title to its Book UID with List Books, and calls Create Book Download Link for the buyer's email address. The link comes back without BookFunnel sending anything, so the store's existing confirmation email carries it and the buyer never sees a second sender. The book is also added to that reader's BookFunnel library under the same address, which is what makes a later re-download work. Fulfillment moves from a task the author does after each sale to a step inside the order flow.
Reader Magnet on Signup
Someone joins the mailing list through a form and the agent needs to deliver the free first in series. Rather than handing delivery to the email platform, the agent calls Create Page Download Link against the opt in landing page and writes the resulting link onto the subscriber record in MailerLite as a custom field, so the welcome sequence renders a link unique to that reader. Links created against a landing page are recorded in that page's CSV export, which is BookFunnel's own record of what was generated and for whom. The author keeps the delivery relationship instead of exporting it.
Advance Review Copy Distribution
A launch is three weeks out and a curated reviewer list needs copies. The agent assembles the addresses, resolves the Book UID with List Books, and prepares an Email Download Link run so BookFunnel does the sending and the links land in the landing page's CSV export as an auditable record. Then it stops. Create Book Download Link and Add Book To Library take a Book UID, while Create Page Download Link and Email Download Link take a Page ID, and BookFunnel names both object on the wire. A single transposed identifier sends the wrong title to every reviewer on the list, and nothing in the API takes it back. The agent presents both identifiers with the resolved title and waits.
Human-in-Loop Highlight
The gate is the moment before a list send, and it exists because BookFunnel has no inverse operation for anything this connector does. The agent assembles the reviewer or promotion list, resolves the title through List Books, and pauses before Email Download Link. It posts to the author's channel: "Ready to send *[resolved title]* to 47 reviewers via Page ID BF-page-8821, Book UID BFXXXXXXXXXX. BookFunnel will send these emails and add the book to each reader's library. There is no way to revoke the links or remove the book afterward. Send, change the title, or hold?" The author answers, and only then does the send run. That gate is not caution for its own sake. It is the correct response to an API where the delivery record, the reader's library entry, and the CSV row are all one way writes, and where the Book UID and Page ID that select what gets sent are two different identifiers that BookFunnel presents under the same field name.
Agent Capabilities
8 actionsDelivery
4- Create Book Download Link Creates a unique BookFunnel download link for a single book and returns it without sending any email, so your own system can deliver the link. The book is also added to the reader's BookFunnel library under the email address supplied. Use this when your flow already sends its own email and only needs the link. To generate a link against an opt in landing page instead of a single book, use Create Page Download Link.
- Create Page Download Link Creates a unique BookFunnel download link against an opt in landing page and returns it without sending any email, so your own system can deliver the link. The book behind the page is also added to the reader's BookFunnel library under the email address supplied. Links created this way are recorded in the landing page's CSV export, which keeps an auditable record of every link generated. To generate a link against a single book instead of a page, use Create Book Download Link.
- Email Download Link Creates a unique download link against an opt in landing page and has BookFunnel email it to the reader, so no sending is needed on your side. The response reports "Email queued" and still returns the link and code. The book is added to the reader's BookFunnel library, and the link is recorded in the landing page's CSV export. Subject, heading and message are optional and fall back to BookFunnel's defaults, which support the merge tags shown in the parameter hints.
- Add Book To Library Adds a book directly to a reader's BookFunnel library for the email address supplied. Unlike the link actions this is documented as generating no download code or link, so use it to grant access without delivering anything to the reader. BookFunnel does not document an inverse operation, so removing a book from a reader's library is not possible through the API.
Catalog
1- List Books Returns the books on the BookFunnel account, which is the only way to discover the Book UID (in the form BFXXXXXXXXXX) that every delivery action requires. This route is not described in the BookFunnel API documentation or OpenAPI spec, so its response is returned exactly as BookFunnel sends it, without reshaping, and the field names it contains have not been verified against a live account.
Account
1- Test Access Verifies that the configured BookFunnel credential is valid and returns the name and email address of the BookFunnel account it belongs to. Use this to confirm a connection before running delivery actions. A valid credential returns status OK with the account name and email. An invalid one fails with "Invalid API Key", and a missing one fails with "No API Key header in request".
Access Tokens
2- Refresh Access Token Exchanges the OAuth2 access token in the connection for a new one and returns it. This applies only when the configured credential is an OAuth2 access token, not a personal API key. BookFunnel access tokens never expire on their own, so refreshing is a deliberate rotation rather than a scheduled necessity. The previous token keeps working for a further 10 minutes to cover failures mid rotation, so follow this with Revoke Access Token if that overlap is unacceptable. The new token must be written back into the connection or subsequent calls continue to use the old one.
- Revoke Access Token Permanently disables the OAuth2 access token in the connection and removes it from BookFunnel. This is irreversible, and every later call using that token fails, including calls from this FlowRunner connection, so run it only against a token you have already replaced. If it is the last token issued to an app for a given user, the app stops appearing as an integration on that user's BookFunnel dashboard. This applies only when the configured credential is an OAuth2 access token, not a personal API key.
Frequently Asked Questions
What can FlowRunner do with BookFunnel?
FlowRunner agents can run Test Access, List Books, and Create Book Download Link in BookFunnel, plus 5 more actions.
Does connecting BookFunnel to FlowRunner require OAuth?
No. BookFunnel connects to FlowRunner with an API key, no OAuth flow required.
Can BookFunnel trigger a FlowRunner workflow automatically?
BookFunnel doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with BookFunnel
$100 in credits. No card required. Connect in minutes.