Integration
Connect FlippingBook to Neon Postgres
When New Flipbook fires in FlippingBook, your agent runs Add project in Neon Postgres. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want FlippingBook and Neon Postgres to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What FlippingBook can start in Neon Postgres
When New Flipbook in FlippingBook
then Add project in Neon Postgres
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with FlippingBook and Neon Postgres
Triggers and actions 1 trigger · 39 actions
- New Flipbook
Triggers when a new flipbook is created in the FlippingBook account.
- Add Flipbook Source
Uploads a new PDF version to an existing flipbook from a public URL; it goes live once conversion finishes.
- Create Flipbook
Creates a new flipbook, optionally converting a PDF from a public URL as its first version.
- Delete Flipbook
Marks a flipbook for deletion; it is removed permanently after a period of time.
- Find Flipbook by ID
Returns one flipbook (publication) by its unique ID, including its name, URL, page count and customization settings.
- Find Flipbook by Public URL
Finds the flipbook whose public URL exactly matches the given URL.
- Find Flipbook by Title
Finds flipbooks whose name contains the given title text and returns the matching flipbooks.
- Get Trackable Link
Returns one trackable link with its state and view statistics.
- List Custom Domains
Returns the custom domains available in the FlippingBook account.
- Update Flipbook
Updates a flipbook's name or description and can replace its content with a new PDF from a public URL.
- Update Trackable Link
Renames a trackable link or disables, re-enables or deletes it.
- Add branch
Create a new branch in a Neon project.
- Add compute endpoint
Creates a compute endpoint (a Neon compute instance) on a branch of a Neon project. A branch can have one read-write endpoint and multiple read-only endpoints.
- Add database
Creates a new Postgres database in a Neon project branch, owned by an existing role.
- Add project
Creates a new Neon Postgres project with its default branch, database, role and compute, and returns the project along with its connection details.
- Add role
Creates a Postgres role in the specified Neon project branch. Connections to the branch's active compute are dropped while the change applies.
- Delete branch
Delete a branch by project_id and branch_id.
- Delete compute endpoint
Deletes a compute endpoint from a Neon project. Existing connections to the compute are dropped. If the compute does not exist or was already deleted, the step still succeeds with an empty result.
- Delete database
Deletes the specified database from a branch of a Neon project.
- Delete project
Deletes a Neon project and all its branches, compute endpoints, databases and roles. The project can be recovered within 7 days.
- Delete role
Deletes the specified Postgres role from a Neon branch.
- Get branch
Retrieves details of a branch in a Neon project.
- Get compute endpoint
Retrieve details about a compute endpoint.
- Get connection URI
Retrieve a Postgres connection URI for a database/role/branch/endpoint combination.
- Get database
Retrieves details of a database on a Neon project branch.
- Get project
Retrieves the details of a Neon project, including its settings, compute configuration, history retention, owner and current usage metrics.
- Get role
Retrieves details about a Postgres role (user) on a Neon branch.
- Get role password
Retrieves the password for a Postgres role on a Neon branch.
- List branches
Retrieve a list of branches for a Neon project.
- List compute endpoints
Lists the compute endpoints (Neon compute instances) in a project.
- List databases
Lists the databases on a branch of a Neon project.
- List operations
Lists the operations (asynchronous actions such as starting a compute or creating a branch) Neon performed on a project. Operations older than 6 months may no longer be available.
- List projects
Lists the Neon projects accessible to the connected account, optionally filtered by name/ID or organization.
- List roles
Lists the Postgres roles on a Neon project branch.
- Start compute endpoint
Start (resume) a suspended compute endpoint.
- Suspend compute endpoint
Suspends the specified Neon compute endpoint (scales it to zero).
- Update branch
Update a branch's properties (e.g. name, protected) by project_id and branch_id.
- Update compute endpoint
Updates an existing compute endpoint in a Neon project by ID.
- Update database
Updates the name or owner of a database on a Neon project branch.
- Update project
Update settings for a Neon project by project_id.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from FlippingBook
FlippingBook to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
FlippingBook to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
FlippingBook to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
FlippingBook to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
FlippingBook to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
FlippingBook to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Neon Postgres
Vimeo OTT to Neon PostgresVimeo OTT (formerly VHX) is an over-the-top video monetization platform for launching subscription and...
Questions
FlippingBook and Neon Postgres, answered
What can start an automation from FlippingBook?
Any of FlippingBook's 1 trigger in the catalog, including New Flipbook. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Neon Postgres when something happens in FlippingBook?
Any of Neon Postgres's 29 actions, including Update branch, Update compute endpoint, Update database and Update project. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Neon Postgres to FlippingBook?
Neon Postgres has no triggers in the catalog today, so automations start in FlippingBook. If you need the other direction, ask: your agent reads Neon Postgres's API documentation and adds it.
Do I have to build a connector for FlippingBook or Neon Postgres?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use FlippingBook and Neon Postgres without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.