Integration
Connect Copper and Reply
When New Activity fires in Copper, your agent runs Add contact list in Reply, or New Email Opened in Reply to Create Lead in Copper. 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 Reply 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 and Reply can do together
From Copper to Reply
When New Activity in Copper
then Add contact list in Reply
When New Company in Copper
then Add note to contact in Reply
From Reply to Copper
When New Email Opened in Reply
then Create Lead in Copper
When New Emails Sent in Reply
then Create Task in Copper
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 Reply
Triggers and actions 24 triggers · 38 actions
Trigger
New ActivityTriggers when a new activity is created.
Trigger
New CompanyTriggers when a new Company is created in Copper.
Trigger
New LeadTriggers when a Lead is created in Copper.
Trigger
New OpportunityTriggers when an Opportunity is created in Copper.
Trigger
New PersonTriggers when a new Person is created in Copper.
Trigger
New ProjectTriggers when a new Project is created in Copper.
Trigger
New TaskTriggers when a new Task is created in Copper.
Trigger
Updated CompanyTriggers when a Person's Company is changed.
Trigger
Updated Contact TypeTriggers when a Person's Contact Type is changed.
Trigger
Updated LeadTriggers when a Lead is changed.
Trigger
Updated Lead StatusTriggers when a Lead's status is changed.
Trigger
Updated OpportunityTriggers when an Opportunity is changed.
Trigger
Updated Opportunity StageTriggers when an Opportunity's stage is changed.
Trigger
Updated Opportunity StatusTriggers when an Opportunity's status is changed.
Trigger
Updated PersonTriggers when a Person is changed.
Trigger
Updated ProjectTriggers when a Project is changed.
Trigger
Updated TaskTriggers when a Task is changed.
Action
Associate to ProjectThis 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.
Action
Create ActivityLogs a new Activity on a Person, Company, Opportunity, or Lead.
Action
Create CompanyCreates a new Company.
Action
Create LeadCreates a new Lead.
Action
Create OpportunityCreates a new Opportunity.
Action
Create PersonCreates a new Person.
Action
Create ProjectCreates a new Project.
Action
Create TaskCreates a new Task.
Action
Create/Update CompanyCreates or Updates a Company depending on the match criteria.
Action
Create/Update LeadCreates or Updates a Lead depending on the match criteria.
Action
Create/Update OpportunityCreates or Updates an Opportunity based off of a match criteria.
Action
Create/Update PersonCreates or Updates a Person depending on the match criteria.
Action
Create/Update ProjectCreates or Updates a Project depending on the match criteria.
Action
Search for a CompanySearches for an existing company in Copper.
Action
Search for an ActivitySearches for an existing activity in Copper.
Action
Search for a OpportunitySearches for an existing opportunity in Copper.
Action
Search for a PersonSearches for an existing person in Copper.
Action
Search for a ProjectSearches for an existing project in Copper.
Action
Update CompanyUpdates a Company depending on the match criteria.
Action
Update OpportunityUpdates an Opportunity based off of a match criteria.
Action
Update PersonUpdates a Person depending on the match criteria.
Action
Update ProjectUpdates a Project depending on the match criteria.
Trigger
Inbox Category Set for ReplyTriggers when an email reply in Reply is given an inbox category, automatically or by a user.
Trigger
New Email OpenedTriggers when a contact opens a tracked email sent from Reply.
Trigger
New Emails SentTriggers when Reply sends an email from a sequence step.
Trigger
New Link ClickedTriggers when a recipient clicks a tracked link in an email sent from Reply.
Trigger
New Person BounceTriggers when an email sent from Reply bounces or is rejected by the recipient's mail server.
Trigger
New Person Opt OutTriggers when a contact opts out of outreach in Reply (unsubscribe link, manual opt-out, or marked Do Not Contact).
Trigger
Prospect FinishedTriggers when a contact's participation in a Reply sequence ends — completed, replied, bounced, opted out, or finished manually.
Action
Add contact listCreates a new contact list in Reply, optionally shared with your team.
Action
Add note to contactAdds a note to a contact's timeline in Reply.
Action
Add sequenceCreates a new sequence in Reply with its steps, schedule, sending accounts and settings.
Action
Create\Update PersonCreates a Reply contact, or updates the existing contact with the same email address.
Action
Delete contactDeletes a contact from your Reply account.
Action
Find contacts by criteriaReturns the contacts that match a search term and/or field rules, optionally scoped to a contact list, sequence or sequence step.
Action
Get contactReturns one Reply contact by its id, including profile details, owner, opt-out, call and meeting status, stage and custom fields.
Action
Get sequenceReturns one sequence in full: name, status, owner, schedule, settings, connected email and LinkedIn accounts, and its steps.
Action
List contact listsReturns the contact lists you own plus those shared with your team, optionally filtered by name.
Action
List contactsReturns your Reply contacts, optionally narrowed to one email address or LinkedIn profile URL.
Action
List inbox categoriesReturns the inbox categories you can file conversations under.
Action
List Sequence ContactsReturns the contacts enrolled in a sequence, with each contact's status, current step, added date, opt-out and call status.
Action
List sequencesReturns the sequences in your Reply account, optionally filtered by status, owner, folder, archive state or name.
Action
Mark as FinishedMarks one or more contacts as finished in every sequence they are in, so they receive no further sequence steps.
Action
Remove Person From CampaignRemoves a contact from a sequence so they stop progressing through it. The contact and their history stay in your Reply account.
Action
Send Test Webhook EventSends a test event from an existing Reply webhook subscription to its configured URL.
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 Reply
HubSpot to ReplyHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to ReplyGoogle Sheets
Gmail to ReplyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ReplyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to ReplyGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to ReplyMailchimp marketing automation and email platform.
Questions
Copper and Reply, 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 Reply when something happens in Copper?
Any of Reply's 16 actions, including Create\Update Person, Send Test Webhook Event, Add contact list and Add note to contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Reply to Copper?
Yes. When something happens in Reply, your agent can act in Copper too. This page covers both directions: Reply's triggers and Copper's actions are listed here as well.
Do I have to build a connector for Copper or Reply?
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.