Integration
Connect DocumentPro and Givebutter
When something happens in DocumentPro or Givebutter, your agent does the next thing in the other. 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 DocumentPro and Givebutter 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 DocumentPro and Givebutter can do together
From DocumentPro to Givebutter
When New Document in DocumentPro
then Create Contact in Givebutter
From Givebutter to DocumentPro
When New Campaign in Givebutter
then Add classifier in DocumentPro
When New Ticket in Givebutter
then Add workflow in DocumentPro
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 DocumentPro and Givebutter
Triggers and actions 5 triggers · 15 actions
Trigger
New DocumentTriggers when a document is uploaded.
Action
Add classifiercreate a new Classifier.
Action
Add workflowcreate a new Workflow (extraction template).
Action
Classify documentclassify a document inline without a saved Classifier.
Action
Delete classifierdelete a Classifier.
Action
Delete workflowdelete a Workflow.
Action
Get classifierfetch a single Classifier by id.
Action
Get documentfetch a single document by id.
Action
Get workflowfetch a single Workflow by id.
Action
List classifierslist saved Classifiers.
Action
Run classifier against documentrun a saved Classifier against a document.
Action
Run workflow against documentStart an extraction Workflow against a document. The run is asynchronous: it returns a request_id immediately and the extracted data arrives once the job completes.
Action
Update classifierupdate an existing Classifier.
Action
Update workflowupdate an existing Workflow.
Action
Upload DocumentUpload a document (PDF, JPEG, PNG or TIFF) up to 6MB so it can be classified or parsed by a workflow.
Trigger
New CampaignTriggers when a new campaign is created.
Trigger
New TicketTriggers when a new ticket is issued.
Trigger
New TransactionTriggers when a new transaction is created.
Trigger
Updated CampaignTriggers when a campaign is updated.
Action
Create ContactCreates a Contact. If there is a contact that already exists with the same First and Last Name, as well as the same Email Or Phone, we will automatically deduplicate and merge the contact, otherwise a new contact will be created. If you'd like to always create a new contact regardless of the deduplication logic, pass the force_create parameter as true.
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 DocumentPro
DocumentPro to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DocumentPro to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
DocumentPro to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
DocumentPro to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
DocumentPro to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
DocumentPro to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
More into Givebutter
Slack to GivebutterSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to GivebutterGoogle Sheets
Google Drive to GivebutterGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to GivebutterMailchimp marketing automation and email platform.
ActiveCampaign to GivebutterActiveCampaign is a marketing automation, email marketing, and CRM platform.
Notion to GivebutterA new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team.
Questions
DocumentPro and Givebutter, answered
What can start an automation from DocumentPro?
Any of DocumentPro's 1 trigger in the catalog, including New Document. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Givebutter when something happens in DocumentPro?
Any of Givebutter's 1 action, including Create Contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Givebutter to DocumentPro?
Yes. When something happens in Givebutter, your agent can act in DocumentPro too. This page covers both directions: Givebutter's triggers and DocumentPro's actions are listed here as well.
Do I have to build a connector for DocumentPro or Givebutter?
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.