Integration
Connect Docupilot to Neon Api Keys
When something happens in Docupilot, your agent does the next thing in Neon Api Keys. Describe it 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 Docupilot and Neon Api Keys to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Docupilot can start in Neon Api Keys
When Envelope Completed in Docupilot
then Add API key in Neon Api Keys
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 Docupilot and Neon Api Keys
Triggers and actions 2 triggers · 47 actions
- Envelope Completed
Triggers when all recipients finish signing an envelope.
- New Envelope
Triggers when a new e-signature envelope is created.
- Cancel Envelope
Cancel an in-progress e-signature envelope.
- Convert Document
Convert a document to another format.
- Copy Template
Duplicate a template including its preferences and deliveries.
- Create Envelope
Create a new e-signature envelope.
- Create Envelope Recipient
Add a recipient to an e-signature envelope.
- Create Folder
Create a new folder.
- Create Template
Create a new document template.
- Create Template Delivery
Configure a new delivery on a template.
- Create Template Merge Link
Create a shareable link that generates a document from a template.
- Delete Folder
Delete a folder.
- Delete Template
Move a template to the trash.
- Get Bulk Generation Task
Retrieve a single bulk document-generation task.
- Get Envelope Details
Retrieve the details of an e-signature envelope.
- Get Envelope Responses
Retrieve the consolidated field responses for an envelope.
- Get Envelope Signing Link
Retrieve the signing link for an envelope.
- Get Template
Retrieve a single template by its id.
- Get Template Schema
Retrieve a template's merge-field schema.
- List Bulk Generation Tasks
List bulk document-generation tasks for a template.
- List Document History
List previously generated documents.
- List Envelope Recipients
List the recipients of an e-signature envelope.
- List Envelopes
List e-signature envelopes.
- List Folders
List the folders in the Docupilot account.
- List Template Deliveries
List the deliveries configured on a template.
- List Templates
List the templates in the Docupilot account.
- Merge Documents
Append and merge multiple documents into one.
- Place Signature Fields
Place the signature/input fields on an envelope's document. Required before Send Envelope: Docupilot rejects sending unless EVERY recipient has at least one field. Replaces the document's whole field set.
- Retry Document Delivery
Retry a failed document delivery.
- Send Envelope
Send an e-signature envelope to its recipients.
- Send Envelope Reminder
Send a signing reminder to an envelope's signers.
- Transform PDF
Apply a transformation to a PDF document.
- Trigger Bulk Generation
Start a prepared bulk document-generation task.
- Update Folder
Update a folder's details.
- Update Template
Update an existing template's settings.
- Upload CSV for Bulk Generation
Upload a CSV to start a bulk document-generation task for a template.
- Add API key
Creates a new personal Neon API key and returns its token.
- Add branch
Creates a branch in a Neon project. By default the branch is forked from the project's default branch with no compute, and Neon generates its name.
- 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 compute and any number of read-only computes.
- Add database
Creates a Postgres database in a branch of a Neon project.
- Add project
Creates a new Neon Postgres project, including 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.
- Delete API key
Revokes (permanently deletes) a Neon API key. This cannot be undone.
- Delete branch
Deletes a branch from a Neon project. Compute endpoints on the branch go idle and existing connections are dropped.
- Delete database
Deletes the specified database from a branch of a Neon project.
- Delete project
Deletes a Neon project along with all of its branches, databases, roles and compute endpoints. Deleted projects can be recovered within 7 days.
- List API keys
Lists the API keys for your Neon account. Key tokens are not returned.
- List projects
List all Neon projects owned by the account.
- Update project
Updates an existing Neon project by ID: its name, history retention period, project settings (quotas, IP allowlist, maintenance window, and more) and default compute settings.
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 Docupilot
Docupilot to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Docupilot to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Docupilot to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Docupilot to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Docupilot to StripeStripe is a payment processing platform for online businesses.
Docupilot to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Neon Api Keys
Slack to Neon Api KeysSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Neon Api KeysGoogle Sheets
Questions
Docupilot and Neon Api Keys, answered
What can start an automation from Docupilot?
Any of Docupilot's 2 triggers in the catalog, including Envelope Completed and New Envelope. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Neon Api Keys when something happens in Docupilot?
Any of Neon Api Keys's 13 actions, including Update project, Add API key, Add branch and Add compute endpoint. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Neon Api Keys to Docupilot?
Neon Api Keys has no triggers in the catalog today, so automations start in Docupilot. If you need the other direction, ask: your agent reads Neon Api Keys's API documentation and adds it.
Do I have to build a connector for Docupilot or Neon Api Keys?
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.
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.