Integration
Connect Pyrus to Namsor
When New Form Task fires in Pyrus, 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 Pyrus 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 Pyrus can start in Namsor
When New Form Task in Pyrus
then Name Type Recognition in Namsor
When New Form Task in Pyrus
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 Pyrus and Namsor
Triggers and actions 1 trigger · 25 actions
Trigger
New Form TaskTriggers when a new task is created from a Pyrus form.
Action
Add MemberAdds a user to the Pyrus organization.
Action
Add Task CommentAdds a comment to a Pyrus task, and can also close or reopen it, approve or reject it, or reassign it.
Action
Delete TaskDeletes a Pyrus task.
Action
Find Catalog ItemsReturns a Pyrus catalog's items, optionally only those whose column matches a value.
Action
Find Form TasksSearches the tasks created from a Pyrus form, by text, step, or creation and modification dates.
Action
Get FormReturns a Pyrus form template with its fields.
Action
Get MemberReturns a Pyrus organization member's profile by ID.
Action
Get TaskReturns a Pyrus task with its fields, participants and comments.
Action
List CatalogsReturns all Pyrus catalogs, without their items.
Action
List FormsReturns all Pyrus form templates the user manages or belongs to.
Action
List MembersReturns all members of the Pyrus organization.
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 Pyrus
Pyrus to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pyrus to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Pyrus to StripeStripe is a payment processing platform for online businesses.
Pyrus to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Pyrus to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pyrus to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
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
Pyrus and Namsor, answered
What can start an automation from Pyrus?
Any of Pyrus's 1 trigger in the catalog, including New Form Task. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Namsor when something happens in Pyrus?
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 Pyrus?
Namsor has no triggers in the catalog today, so automations start in Pyrus. 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 Pyrus 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 Pyrus 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.