Integration
Connect DocuPipe and Keplars
When Document Processed fires in DocuPipe, your agent runs Add Contact to Audience in Keplars, or New Audience in Keplars to Upload Document in DocuPipe. 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 DocuPipe and Keplars 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 DocuPipe and Keplars can do together
From DocuPipe to Keplars
When Document Processed in DocuPipe
then Add Contact to Audience in Keplars
When Document Processed in DocuPipe
then Send Email in Keplars
From Keplars to DocuPipe
When New Audience in Keplars
then Upload Document in DocuPipe
When New Contact in Audience in Keplars
then Analyze document in DocuPipe
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 DocuPipe and Keplars
Triggers and actions 3 triggers · 35 actions
Trigger
Document ProcessedTriggers when a document finishes parsing and OCR is complete.
Action
Add schemaCreates a new extraction schema in DocuPipe from a JSON schema you supply, and returns its schema ID.
Action
Analyze documentAsks DocuPipe a list of plain-language questions about one document and starts the analysis, returning the analysis ID to fetch the answers with.
Action
Classify DocumentSends one or more documents to DocuPipe to be sorted into your classes, and returns the job that is doing the work.
Action
Delete documentRemoves a document from your DocuPipe account.
Action
Delete schemaRemoves an extraction schema from your DocuPipe account.
Action
Extract Data From DocumentPulls structured data out of a document using one of your schemas, and returns the extraction to fetch the results with.
Action
Find documents by criteriaFinds documents in your DocuPipe account whose file name or document ID matches what you search for.
Action
Get DocumentReturns one document from your DocuPipe account, with its file details, processing status, parsed text and your own metadata.
Action
Get Extraction ResultReturns the data DocuPipe pulled out of a document, shaped by the schema that was used, along with per-field confidence details.
Action
Get schemaReturns one extraction schema from your DocuPipe account, including the JSON schema it applies and its guidelines.
Action
List documentsReturns the documents in your DocuPipe account, optionally narrowed to one dataset or a date range.
Action
List extractionsReturns the data extractions in your DocuPipe account, optionally narrowed to one schema, one document, or a specific set of extractions.
Action
List schemasReturns the extraction schemas in your DocuPipe account.
Action
Upload and Extract DataSends a file to DocuPipe and immediately starts pulling structured data out of it, returning both the new document and the extraction.
Action
Upload DocumentSends a file to DocuPipe to be read and turned into a document you can extract data from.
Trigger
New AudienceTriggers when a new audience is created.
Trigger
New Contact in AudienceTriggers when a contact is added to an audience.
Action
Add Contact to AudienceAdds a contact to an audience, reusing an existing contact with the same email.
Action
Add DomainAdds a sending domain and returns the DNS records to publish.
Action
Create AudienceCreates a new audience (contact list).
Action
Delete AudienceDeletes an audience.
Action
Delete ContactDeletes a contact.
Action
Delete DomainDeletes a sending domain.
Action
Enroll Contact in AutomationEnrolls a contact, by email, in a Keplars automation.
Action
Get AudienceReturns one audience by its ID.
Action
Get AutomationReturns one automation by its ID.
Action
Get ContactReturns one contact, looked up by ID or email.
Action
List AudiencesReturns the workspace's audiences.
Action
List AutomationsReturns the workspace's automations.
Action
List Contacts in AudienceReturns the contacts in an audience.
Action
List DomainsReturns the workspace's sending domains.
Action
Remove Contact from AutomationRemoves a contact, by email, from a Keplars automation.
Action
Schedule EmailSchedules a transactional email to be sent at a future date and time.
Action
Send EmailQueues a transactional email for delivery through Keplars.
Action
Track EventRecords a custom event for a contact, which can start event-triggered Keplars automations.
Action
Update ContactUpdates a contact's details.
Action
Verify DomainChecks a sending domain's DNS records and returns its verification result.
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 DocuPipe
DocuPipe to PubloraPublish and schedule posts to ten social networks from one endpoint
DocuPipe to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DocuPipe to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
DocuPipe to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
DocuPipe to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
DocuPipe to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Keplars
HubSpot to KeplarsHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to KeplarsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to KeplarsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to KeplarsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to KeplarsGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to KeplarsActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
DocuPipe and Keplars, answered
What can start an automation from DocuPipe?
Any of DocuPipe's 1 trigger in the catalog, including Document Processed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Keplars when something happens in DocuPipe?
Any of Keplars's 20 actions, including Create Audience, Send Email, Update Contact and Add Contact to Audience. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Keplars to DocuPipe?
Yes. When something happens in Keplars, your agent can act in DocuPipe too. This page covers both directions: Keplars's triggers and DocuPipe's actions are listed here as well.
Do I have to build a connector for DocuPipe or Keplars?
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 DocuPipe and Keplars 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.