Integration
Connect Confetti to Namsor
When Contact Created fires in Confetti, your agent runs Name Type Recognition in Namsor. 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 Confetti and Namsor 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 Confetti can start in Namsor
When Contact Created in Confetti
then Name Type Recognition in Namsor
When Contact Updated in Confetti
then Split Full Name in Namsor
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 Confetti and Namsor
Triggers and actions 12 triggers · 53 actions
Trigger
Contact CreatedTriggers when a new contact is added to your workspace.
Trigger
Contact UpdatedTriggers when a contact is added or changed.
Trigger
Event CreatedTriggers when a new event is created.
Trigger
Event UpdatedTriggers when an event is created or changed.
Trigger
Payment PaidTriggers when a payment for an event is paid.
Trigger
Payment RefundedTriggers when a payment for an event is refunded.
Trigger
Ticket AttendingTriggers when someone is attending an event.
Trigger
Ticket DeclinedTriggers when someone declines an event.
Trigger
Ticket Deletion RequestedTriggers when someone asks to be removed from an event.
Trigger
Ticket InvitedTriggers when someone is invited to an event.
Trigger
Ticket UpdatedTriggers when a ticket for an event is added or changed.
Trigger
Ticket WaitlistedTriggers when someone is put on an event's waitlist.
Action
Contact AddAdds a contact to your Confetti workspace.
Action
Create BlockCreates a block in Confetti.
Action
Create EventCreates a event in Confetti.
Action
Create Form FieldCreates a form field in Confetti.
Action
Create ImageCreates a image in Confetti.
Action
Create OrganiserCreates a organiser in Confetti.
Action
Create PageCreates a page in Confetti.
Action
Create Schedule ItemCreates a schedule item in Confetti.
Action
Create SpeakerCreates a speaker in Confetti.
Action
Create SponsorCreates a sponsor in Confetti.
Action
Create Sponsor LevelCreates a sponsor level in Confetti.
Action
Get BlockReturns one block by its ID.
Action
Get CategoryReturns one category by its ID.
Action
Get ContactReturns one contact by its ID.
Action
Get EventReturns one event by its ID.
Action
Get FormReturns one form by its ID.
Action
Get Form FieldReturns one form field by its ID.
Action
Get ImageReturns one image by its ID.
Action
Get OrganiserReturns one organiser by its ID.
Action
Get PageReturns one page by its ID.
Action
Get PaymentReturns one payment by its ID.
Action
Get Schedule ItemReturns one schedule item by its ID.
Action
Get SpeakerReturns one speaker by its ID.
Action
Get SponsorReturns one sponsor by its ID.
Action
Get Sponsor LevelReturns one sponsor level by its ID.
Action
Get TicketReturns one ticket by its ID.
Action
Get Ticket BatchReturns one ticket batch by its ID.
Action
Get WorkspaceReturns one workspace by its ID.
Action
List BlocksReturns a page of blocks.
Action
List CategoriesReturns a page of categories.
Action
List ContactsReturns a page of contacts.
Action
List EventsReturns a page of events.
Action
List ImagesReturns a page of images.
Action
List PagesReturns a page of pages.
Action
List PaymentsReturns a page of payments.
Action
List Ticket BatchesReturns a page of ticket batches.
Action
List TicketsReturns a page of tickets.
Action
Ticket AddAdds a person straight to an event's attendee list, skipping the invitation.
Action
Ticket InviteInvites a person to an event.
Action
Get Country From First/Last NameReturns the most likely country of residence for a person from their first name and/or last name, with the runner-up country, region, top 10 candidate countries and calibrated probabilities.
Action
Get Country From Full NameReturns the most likely country of residence for a person's unsplit full name, with the runner-up country, region, the top 10 likely countries and calibrated probabilities.
Action
Get Ethnicity From First/Last NameReturns the most likely ethnicity or diaspora for a person's first and last name, with a ranked top 10 and calibrated probabilities, optionally in the context of a country of residence.
Action
Get Ethnicity From Full NameReturns the most likely ethnicity or diaspora of a person from their full name, optionally in the context of their country of residence, with the top 10 likely ethnicities and calibrated probabilities.
Action
Get Gender From a Full NameReturns the most likely gender of a person from their unsplit full name, with a gender scale and a calibrated probability.
Action
Get Gender From First/Last NameReturns the most likely gender (male or female) for a person's first name and optional last name, with a gender scale and a calibrated probability.
Action
Get Indian Caste Group From First/Last NameReturns the most likely Indian caste group (General, OBC, SC or ST) for a person's first and last name and their Indian state or Union territory, with alternatives and confidence scores.
Action
Get Indian Caste Group From Full NameReturns the most likely Indian caste group (General, OBC, SC or ST) for an unsplit Indian full name and the person's Indian state or union territory.
Action
Get Origin From First/Last NameReturns the most likely country of origin for a person's first and/or last name, with region, the top 10 candidate countries and calibrated probabilities.
Action
Get Origin From Full NameReturns the most likely country of origin for a person's full name, with the region, alternative country, top 10 candidate countries and calibrated probabilities.
Action
Get U.S. Race Ethnicity From First/Last NameReturns the most likely U.S. Census race/ethnicity category for a person's first and/or last name, with the second most likely category, ranked alternatives and confidence scores.
Action
Get U.S. Race Ethnicity From Full NameReturns the most likely U.S. race/ethnicity (U.S. Census categories) for a person's full name, with the runner-up category and calibrated probabilities.
Action
Name Type RecognitionClassifies a proper noun as a personal name (anthroponym), a place name (toponym), a brand name or a pseudonym, and returns the most likely and second most likely type with a reliability score.
Action
Split Full NameSplits a person's full name into its most likely first name and last name, with the detected name structure and a reliability score.
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 Confetti
Confetti to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Confetti to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Confetti to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Confetti to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Confetti to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Confetti to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Namsor
HubSpot to NamsorHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to NamsorSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to NamsorSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to NamsorGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to NamsorGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to NamsorGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Confetti and Namsor, answered
What can start an automation from Confetti?
Any of Confetti's 12 triggers in the catalog, including Contact Created, Contact Updated, Event Created and Event Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Namsor when something happens in Confetti?
Any of Namsor's 14 actions, including Get Country From First/Last Name, Get Country From Full Name, Get Ethnicity From First/Last Name and Get Ethnicity From Full Name. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Namsor to Confetti?
Namsor has no triggers in the catalog today, so automations start in Confetti. If you need the other direction, ask: your agent reads Namsor's API documentation and adds it.
Do I have to build a connector for Confetti or Namsor?
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 Confetti and Namsor 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.