Integration
Connect AddEvent and Plecto
When New Calendar fires in AddEvent, your agent runs Create Data Source in Plecto, or New Registration in Plecto to Create Event in AddEvent. 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 AddEvent and Plecto 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)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 AddEvent and Plecto can do together
From AddEvent to Plecto
When New Calendar in AddEvent
then Create Data Source in Plecto
From Plecto to AddEvent
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 AddEvent and Plecto
Triggers and actions 5 triggers · 24 actions
- New Calendar
Triggers when a new calendar is created in AddEvent.
- New Calendar Subscriber
Triggers when someone subscribes to an AddEvent calendar.
- New Event
Triggers when a new event is created in AddEvent.
- New RSVP Attendee
Triggers when a new attendee RSVPs to an AddEvent event.
- Create Calendar
Creates a new AddEvent calendar.
- Create Event
Creates an event on an AddEvent calendar and returns it with its add-to-calendar links.
- Create RSVP Attendee
Adds an RSVP attendee to an AddEvent event.
- Delete Calendar
Permanently deletes an AddEvent calendar.
- Delete Event
Permanently deletes an AddEvent event.
- Delete RSVP Attendee
Deletes an RSVP attendee.
- Get Calendar
Returns one AddEvent calendar by its ID.
- Get Event
Returns one AddEvent event by its ID.
- Get RSVP Attendee
Returns one RSVP attendee by ID.
- List Calendars
Returns the calendars on the AddEvent account.
- Update Calendar
Updates an AddEvent calendar; only the fields you fill in change.
- Update Event
Updates an AddEvent event; only the fields you fill in change.
- Update RSVP Attendee
Updates an RSVP attendee's email or response.
- New Registration
Triggers when a new registration is added to the chosen data source.
- Create Data Source
Creates a new API data source with one field. More fields can be added in Plecto's data source settings.
- Create Member
Creates an employee in Plecto, without login access unless an invite is requested.
- Create Team
Creates a team in Plecto.
- Delete Registration
Permanently deletes one registration from a data source.
- Find Members
Returns employees, optionally only the one with a given external system and ID.
- Get Registration
Returns one registration from a data source.
- List Dashboards
Returns the organization's dashboards.
- List Data Sources
Returns the organization's data sources with their fields.
- List Registrations
Returns registrations, optionally filtered by data source, date range or external ID.
- List Teams
Returns all teams in the organization.
- Update Registration
Updates an existing registration in a data source.
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 AddEvent
AddEvent to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
AddEvent to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
AddEvent to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
AddEvent to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
AddEvent to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
AddEvent to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Plecto
Google Drive to PlectoGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PlectoMailchimp marketing automation and email platform.
Questions
AddEvent and Plecto, answered
What can start an automation from AddEvent?
Any of AddEvent's 4 triggers in the catalog, including New Calendar, New Calendar Subscriber, New Event and New RSVP Attendee. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Plecto when something happens in AddEvent?
Any of Plecto's 11 actions, including Create Data Source, Create Member, Create Team and Update Registration. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Plecto to AddEvent?
Yes. When something happens in Plecto, your agent can act in AddEvent too. This page covers both directions: Plecto's triggers and AddEvent's actions are listed here as well.
Do I have to build a connector for AddEvent or Plecto?
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 AddEvent and Plecto 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.