Integration
Connect Givebutter and Zendesk
When New Campaign fires in Givebutter, your agent runs Add Comment to Ticket in Zendesk, or New Messaging Conversation in Zendesk to Create Contact in Givebutter. 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 Givebutter and Zendesk 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 Givebutter and Zendesk can do together
From Givebutter to Zendesk
When New Campaign in Givebutter
then Add Comment to Ticket in Zendesk
From Zendesk to Givebutter
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 Givebutter and Zendesk
Triggers and actions 7 triggers · 19 actions
- New Campaign
Triggers when a new campaign is created.
- New Ticket
Triggers when a new ticket is issued.
- New Transaction
Triggers when a new transaction is created.
- Updated Campaign
Triggers when a campaign is updated.
- Create Contact
Creates 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.
- New Messaging Conversation
Triggers when a customer starts a new conversation through Zendesk messaging (the web widget, mobile SDK or a social messaging channel). Each conversation arrives as its Zendesk ticket.
- New Ticket
Polling trigger that fires when a new ticket is created.
- New User
Polling trigger that fires when a new user is created.
- Add Comment to Ticket
Adds a public or private comment to an existing ticket.
- Create Organization
Creates a new organization.
- Create Ticket
Creates a new ticket in Zendesk.
- Create User
Creates a new user (end-user or agent).
- Delete Ticket
Deletes a ticket by ID.
- Delete User
Soft-deletes a user by ID.
- Get Messaging User ID
Returns the Zendesk messaging ID for a user, so their messaging conversation can be looked up in Zendesk Messaging.
- Get Organization
Retrieves a single organization by ID.
- Get Ticket
Retrieves a single ticket by ID.
- Get User
Retrieves a single user by ID.
- List Organizations
Lists organizations in the account.
- List Ticket Comments
Lists all comments on a ticket.
- List Tickets
Lists tickets in the account.
- Search
Runs a Zendesk search query across tickets, users, and organizations.
- Search Users
Searches users by query (name, email, etc.).
- Update Organization
Updates an existing organization by ID.
- Update Ticket
Updates an existing ticket by ID.
- Update User
Updates an existing user by 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 Givebutter
Givebutter to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Givebutter to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Givebutter to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Givebutter to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Givebutter to StripeStripe is a payment processing platform for online businesses.
Givebutter to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Zendesk
Slack to ZendeskSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to ZendeskGoogle Sheets
Questions
Givebutter and Zendesk, answered
What can start an automation from Givebutter?
Any of Givebutter's 4 triggers in the catalog, including New Campaign, New Ticket, New Transaction and Updated Campaign. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Zendesk when something happens in Givebutter?
Any of Zendesk's 18 actions, including Create Organization, Create Ticket, Create User and Update Organization. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Zendesk to Givebutter?
Yes. When something happens in Zendesk, your agent can act in Givebutter too. This page covers both directions: Zendesk's triggers and Givebutter's actions are listed here as well.
Do I have to build a connector for Givebutter or Zendesk?
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.