Integration
Connect Kulea to GenderAPI.io
When Form Completed fires in Kulea, your agent runs Find Gender via Email in GenderAPI.io. 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 Kulea and GenderAPI.io 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 Kulea can start in GenderAPI.io
When Form Completed in Kulea
then Find Gender via Email in GenderAPI.io
When New or Updated CRM Data in Kulea
then Validate phone number in GenderAPI.io
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 Kulea and GenderAPI.io
Triggers and actions 9 triggers · 11 actions
Trigger
Email Bounced EventTriggers when a Kulea email hard-bounces.
Trigger
Email Opened EventTriggers when a contact opens a Kulea email.
Trigger
File Downloaded EventTriggers when a contact downloads a file from Kulea.
Trigger
Form CompletedTriggers when a contact completes a Kulea form.
Trigger
Landing Page Visit EventTriggers when a contact visits a Kulea landing page.
Trigger
Link Clicked EventTriggers when a contact clicks a link in a Kulea email.
Trigger
New or Updated CRM DataTriggers when a Kulea contact is added or its CRM data changes.
Trigger
UnsubscribeTriggers when a contact unsubscribes from Kulea emails.
Trigger
Webpage VisitTriggers when a contact visits a tracked page on your own website.
Action
Archive ContactArchives a Kulea contact, which also unsubscribes it.
Action
Create New ContactCreates a new Kulea contact. The email address must be unique.
Action
Find ContactFinds Kulea contacts whose email matches the address you give.
Action
Get ContactReturns one Kulea contact by its ID.
Action
List Contact FieldsReturns the fields on Kulea contact records and their types.
Action
Find Gender in BatchPredicts the gender for up to 50 names, email addresses or usernames in one request, returning a result for each item plus a summary of how many were identified, unknown or failed.
Action
Find Gender via EmailPredicts the likely gender of the person behind an email address, returning the detected first name, gender, country and a confidence score.
Action
Find Gender via NamePredicts the gender of a person from their first name, optionally narrowed to a country, and returns the gender, confidence and matching details.
Action
Find Gender via UsernamePredicts the likely gender behind a username or nickname, returning the gender, a confidence score, where the answer came from and the credits used.
Action
Get usageReturns your GenderAPI.io account's remaining credit balance and when it expires or resets. Checking usage is free.
Action
Validate phone numberChecks whether a phone number is structurally valid and returns it in international (E.164) format with its country. It checks the number's format, not whether the line is in service.
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 Kulea
Kulea to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Kulea to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Kulea to MailchimpMailchimp marketing automation and email platform.
Kulea to StripeStripe is a payment processing platform for online businesses.
Kulea to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Kulea to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into GenderAPI.io
HubSpot to GenderAPI.ioHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to GenderAPI.ioSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to GenderAPI.ioSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to GenderAPI.ioGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to GenderAPI.ioGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to GenderAPI.ioGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Kulea and GenderAPI.io, answered
What can start an automation from Kulea?
Any of Kulea's 9 triggers in the catalog, including Form Completed, New or Updated CRM Data, Email Bounced Event and Email Opened Event. Describe the moment in plain language and your agent picks the right one.
What can your agent do in GenderAPI.io when something happens in Kulea?
Any of GenderAPI.io's 6 actions, including Find Gender in Batch, Find Gender via Email, Find Gender via Name and Find Gender via Username. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from GenderAPI.io to Kulea?
GenderAPI.io has no triggers in the catalog today, so automations start in Kulea. If you need the other direction, ask: your agent reads GenderAPI.io's API documentation and adds it.
Do I have to build a connector for Kulea or GenderAPI.io?
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 Kulea and GenderAPI.io 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.