Integration
Connect Moxie and Reply
When Client Created fires in Moxie, your agent runs Add contact list in Reply, or New Email Opened in Reply to Create & Optionally Send Invoice in Moxie. 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 Moxie 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 Moxie and Reply can do together
From Moxie to Reply
When Client Created in Moxie
then Add contact list in Reply
When Client Updated in Moxie
then Add note to contact in Reply
From Reply to Moxie
When New Email Opened in Reply
then Create & Optionally Send Invoice in Moxie
When New Emails Sent in Reply
then Create Task in Moxie
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 Moxie and Reply
Triggers and actions 37 triggers · 28 actions
Trigger
Agreement SentTriggers when a proposal is sent either via link or email.
Trigger
Agreement SignedTriggers when an agreement is accepted and signed with e-signature.
Trigger
Agreement ViewedTriggers when a user views the proposal.
Trigger
Client CreatedTriggers when a new client is created in Moxie.
Trigger
Client DeletedTriggers when a client record is deleted in Moxie.
Trigger
Client UpdatedTriggers when a client record is updated in Moxie.
Trigger
Form CompletedTriggers when a form is completed.
Trigger
Invoice SentTriggers when an invoice is sent in Moxie.
Trigger
Meeting CancelledTriggers when a meeting is cancelled
Trigger
Meeting ScheduledTriggers when a new meeting is scheduled
Trigger
Meeting UpdatedTriggers when a meeting is updated or rescheduled
Trigger
Opportunity CreatedTriggered with a pipeline opportunity is created
Trigger
Opportunity DeletedTriggered with a pipeline opportunity is deleted
Trigger
Opportunity UpdatedTriggered with a pipeline opportunity is updated
Trigger
Payment ReceivedTriggers when a payment is received either vial Stripe or manual entry.
Trigger
Project CompletedTriggers when a project is set to "complete" in Moxie.
Trigger
Project CreatedTriggers when a new project is created in Moxie.
Trigger
Project UpdatedTriggers when the settings for a project are updated.
Trigger
Task ApprovalTriggers when a new Deliverable is ready for client approval.
Trigger
Task CreatedTriggered when a Project Task is created
Trigger
Task DeletedTriggered when a Project Task is deleted
Trigger
Task UpdatedTriggered with a Project Task is updated.
Trigger
Ticket ClosedTriggers and a support ticket is closed
Trigger
Ticket CommentTriggers when a comment is created on a ticket
Trigger
Ticket CreatedTriggers when a new support ticket is created
Trigger
Ticket DeletedTriggers when a support ticket is deleted
Trigger
Ticket UpdatedTriggers when a support ticket is updated
Trigger
Time Worked CreatedTriggers when a new time worked entry is created.
Trigger
Time Worked DeletedTriggers when a time worked record is deleted.
Trigger
Time Worked UpdatedTriggers when a time worked entry has been updated.
Action
Create ClientCreates a new client record in Hectic
Action
Create ExpenseRecords a new expense in your Moxie accounting records, optionally filed under a vendor and allocated to a client.
Action
Create OpportunityCreate a new pipeline opportunity
Action
Create & Optionally Send InvoiceCreates an invoice for a client from the line items you supply, and emails it straight away when you fill in who to send it to. Left blank, the invoice is saved as a draft.
Action
Create or Update Calendar EventCreate or update a calendar event in Moxie
Action
Create ProjectCreate a project and optionally use a template
Action
Create TaskCreate a task in the project management system
Action
Create TicketCreate a Ticket for a client and contact
Action
Create Ticket CommentAdds a comment (public or private) to an existing ticket.
Action
Create Time WorkedCreates a time worked entry
Action
Delete Calendar EventDeletes a calendar event in Moxie by the external ID.
Action
Find a ClientFinds a client by either name or contact email address.
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 Moxie
Moxie to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Moxie to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Moxie to Google SheetsGoogle Sheets
Moxie to StripeStripe is a payment processing platform for online businesses.
Moxie to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Moxie to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
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
Moxie and Reply, answered
What can start an automation from Moxie?
Any of Moxie's 30 triggers in the catalog, including Client Created, Client Updated, Form Completed and Meeting Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Reply when something happens in Moxie?
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 Moxie?
Yes. When something happens in Reply, your agent can act in Moxie too. This page covers both directions: Reply's triggers and Moxie's actions are listed here as well.
Do I have to build a connector for Moxie 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.