Integration
Connect Copper to Hippo
When New Activity fires in Copper, your agent runs Create Summary of Ticket History in Hippo. 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 Copper and Hippo 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 Copper can start in Hippo
When New Activity in Copper
then Create Summary of Ticket History in Hippo
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 Copper and Hippo
Triggers and actions 17 triggers · 35 actions
- New Activity
Triggers when a new activity is created.
- New Company
Triggers when a new Company is created in Copper.
- New Lead
Triggers when a Lead is created in Copper.
- New Opportunity
Triggers when an Opportunity is created in Copper.
- New Person
Triggers when a new Person is created in Copper.
- New Project
Triggers when a new Project is created in Copper.
- New Task
Triggers when a new Task is created in Copper.
- Updated Company
Triggers when a Person's Company is changed.
- Updated Contact Type
Triggers when a Person's Contact Type is changed.
- Updated Lead
Triggers when a Lead is changed.
- Updated Lead Status
Triggers when a Lead's status is changed.
- Updated Opportunity
Triggers when an Opportunity is changed.
- Updated Opportunity Stage
Triggers when an Opportunity's stage is changed.
- Updated Opportunity Status
Triggers when an Opportunity's status is changed.
- Updated Person
Triggers when a Person is changed.
- Updated Project
Triggers when a Project is changed.
- Updated Task
Triggers when a Task is changed.
- Associate to Project
This Action allows you to relate an existing Project to and existing CRM object; both objects have to exist before you run this Action. This Action expects two ID's for input: the ID of the CRM record you want to relate to and the Project ID you want to relate it with. This Action was designed to be used in multi-step Zaps, where you already have a Project ID and an related record ID (e.g. a Person) from previous steps.
- Create Activity
Logs a new Activity on a Person, Company, Opportunity, or Lead.
- Create Company
Creates a new Company.
- Create Lead
Creates a new Lead.
- Create Opportunity
Creates a new Opportunity.
- Create Person
Creates a new Person.
- Create Project
Creates a new Project.
- Create Task
Creates a new Task.
- Create/Update Company
Creates or Updates a Company depending on the match criteria.
- Create/Update Lead
Creates or Updates a Lead depending on the match criteria.
- Create/Update Opportunity
Creates or Updates an Opportunity based off of a match criteria.
- Create/Update Person
Creates or Updates a Person depending on the match criteria.
- Create/Update Project
Creates or Updates a Project depending on the match criteria.
- Search for a Company
Searches for an existing company in Copper.
- Search for an Activity
Searches for an existing activity in Copper.
- Search for a Opportunity
Searches for an existing opportunity in Copper.
- Search for a Person
Searches for an existing person in Copper.
- Search for a Project
Searches for an existing project in Copper.
- Update Company
Updates a Company depending on the match criteria.
- Update Opportunity
Updates an Opportunity based off of a match criteria.
- Update Person
Updates a Person depending on the match criteria.
- Update Project
Updates a Project depending on the match criteria.
- Add custom event
Create a custom event for a user (Automation/Create custom event in Hippo Postman docs): app_secret_key, user_unique_key, event_type, etc.
- Create Conversation
Creates a new conversation in the system
- Create or Update User
Create a new user or update an existing one
- Create Summary of Ticket History
Creates a summary of all notes and comments added in the ticket
- Create Ticket
Creates a new ticket in the system
- Get ticket
Get ticket details by ticket_id. POST to Hippo ticketing API (Ticketing/Get Ticket Details in the Postman docs) with ticket_id, app_secret_key.
- List conversations
Fetch a customer's conversation list (Chat/Fetch customer conversation list): email, app_secret_key, start, limit.
- List messages
Fetch messages and chat details for a channel (Chat/Fetch messages and chat details): channel_id, app_secret_key, start, limit.
- Send Broadcast to Users
Sends broadcast messages through hippo
- Send Message
Sends a message in an existing chat
- Update Due Date of Ticket
Updates due date of an existing ticket
- Update Ticket Priority
Updates the priority of a ticket
- Update Ticket Status
Update status of a ticket
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 Copper
Copper to LeadSimpleLeadSimple is the CRM that property management and real estate companies use to scale and grow.
Copper to NvidiaAPI platform for deploying GPU-accelerated AI models, including inference microservices and a container...
Copper to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Copper to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Copper to Google SheetsGoogle Sheets
Copper to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
More into Hippo
Outlign to HippoOutlign is a simple Project Management tool for Creative Teams
Slack to HippoSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Gmail to HippoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Copper and Hippo, answered
What can start an automation from Copper?
Any of Copper's 17 triggers in the catalog, including New Activity, New Company, New Lead and New Opportunity. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Hippo when something happens in Copper?
Any of Hippo's 13 actions, including Create Conversation, Create or Update User, Create Summary of Ticket History and Create Ticket. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Hippo to Copper?
Hippo has no triggers in the catalog today, so automations start in Copper. If you need the other direction, ask: your agent reads Hippo's API documentation and adds it.
Do I have to build a connector for Copper or Hippo?
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.