Integration
Connect InEvent and Reply
When New Attendee fires in InEvent, your agent runs Add contact list in Reply, or New Email Opened in Reply to Create Event in InEvent. 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 InEvent and Reply to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 InEvent and Reply can do together
From InEvent to Reply
When New Attendee in InEvent
then Add contact list in Reply
When New Event in InEvent
then Add note to contact in Reply
From Reply to InEvent
When New Email Opened in Reply
then Create Event in InEvent
When New Emails Sent in Reply
then Update Event in InEvent
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 InEvent and Reply
Triggers and actions 9 triggers · 23 actions
Trigger
New AttendeeTriggers when a new attendee is enrolled in an InEvent event.
Trigger
New EventTriggers when a new event is created in your InEvent company.
Action
Create AttendeeAdds an attendee to an InEvent event and returns the new attendee.
Action
Create EventCreates a new event in your InEvent company and returns it.
Action
Find AttendeesFinds attendees of an InEvent event by name, email or company.
Action
Remove AttendeeRemoves an attendee from an InEvent event.
Action
Search EventsFinds events in your InEvent company, optionally filtered by name or city.
Action
Set Attendee Custom FieldsSets an attendee's custom field answers at an InEvent event.
Action
Update AttendeeUpdates one field of an attendee at an InEvent event and returns the updated attendee.
Action
Update EventUpdates one field of an InEvent event and returns the event.
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.
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 InEvent
InEvent to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
InEvent to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
InEvent to MailchimpMailchimp marketing automation and email platform.
InEvent to StripeStripe is a payment processing platform for online businesses.
InEvent to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
InEvent 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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
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
InEvent and Reply, answered
What can start an automation from InEvent?
Any of InEvent's 2 triggers in the catalog, including New Attendee and New Event. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Reply when something happens in InEvent?
Any of Reply's 15 actions, including Create\Update Person, Add contact list, Add note to contact and Add sequence. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Reply to InEvent?
Yes. When something happens in Reply, your agent can act in InEvent too. This page covers both directions: Reply's triggers and InEvent's actions are listed here as well.
Do I have to build a connector for InEvent 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.
Can my AI client use InEvent and Reply without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.