Integration
Connect Cliengo to Real Phone Validation
When Cliente Nuevo/Actualizado - New/Updated Customer fires in Cliengo, your agent runs Active Phone Check in Real Phone Validation. 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 Cliengo and Real Phone Validation 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 Cliengo can start in Real Phone Validation
When Cliente Nuevo/Actualizado - New/Updated Customer in Cliengo
then Active Phone Check in Real Phone Validation
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 Cliengo and Real Phone Validation
Triggers and actions 2 triggers · 29 actions
- Cliente Nuevo/Actualizado - New/Updated Customer
Triggers when a Cliengo contact (customer) is created or updated.
- Nuevo Cliente - New Customer
Triggers when a new contact (customer) is created in Cliengo.
- Actualizar Cliente / Update Customer
Updates an existing Cliengo contact's name, email, phone, status or assigned agent.
- Add contact note
Adds a text note to a Cliengo contact.
- Add conversation
Creates a new conversation in the Cliengo inbox on a given channel for a visitor.
- Assign conversation to operator
Assigns a conversation to an operator and returns the updated conversation.
- Buscar Agente / Search Agent
Finds agents (users/operators) in your Cliengo account whose name or email matches the text you enter.
- Buscar Contacto / Search Customer
Searches your Cliengo contacts by name, email, phone or other filters and returns the matching contacts.
- Close conversation
Closes a Cliengo inbox conversation, recording whether it resulted in a lead.
- Crear Cliente / Create Customer
Creates a new contact (customer) in Cliengo on the chosen channel.
- Delete contact
Deletes a contact from your Cliengo account.
- Get contact
Returns a single Cliengo contact (lead) by its id, including its status, rating, channel and campaign attribution.
- Get conversation
Returns a single inbox conversation by its ID, including channel, status, assignment, phase, tags and participants.
- List channels
Returns all active channels on the Cliengo account (websites, WhatsApp, Facebook, Instagram), each with its connection status and assigned chatbot.
- List conversation messages
Returns the messages of a Cliengo conversation in chronological order, optionally including system command events.
- List phases
Returns every phase (pipeline stage) of the conversation inbox, with its name and position.
- List tags
Returns every operator tag defined in the Cliengo account, with its name and color.
- List users
Returns the users (agents and operators) of your Cliengo company, with their name, email, role and active status.
- List WhatsApp templates
Returns the WhatsApp message templates (approved, pending and rejected) of a WhatsApp channel.
- Send message
Sends a message (text, image, command or note) into a Cliengo conversation on behalf of an operator, the chatbot or the visitor.
- Send WhatsApp template message
Sends an approved WhatsApp template message to one or more recipients through a WhatsApp Business channel.
- Update conversation phase
Moves a conversation to the chosen phase of your pipeline.
- Active Phone Check
Checks whether a US phone number is active on an in-business phone service provider, and whether it is a landline, cell or VoIP line.
- Do Not Call Lookup
Checks whether a US phone number is on the National, State or DMA Do Not Call lists or tied to a known TCPA litigator, and returns its phone type.
- Do Not Call Plus
Checks whether a US phone number is connected or disconnected and whether it is on the National, State or DMA Do Not Call lists or tied to a known TCPA litigator, plus its phone type.
- Scrub Phone Number Validator
Checks whether a US phone number is connected or disconnected (a small share may come back unknown). Suited to large lists.
- Scrub Plus Phone Validator
Checks whether a US phone number is connected or disconnected (a small share may come back unknown) and returns its phone type. Suited to large lists.
- Turbo Phone Validator (Deprecated)
Checks whether a US phone number is connected or disconnected and returns its carrier and whether it is a cell phone. Superseded by Turbo V3.
- Turbo Standard Phone Validator
Checks whether a US phone number is connected or disconnected and returns its phone type (mobile, landline or VoIP).
- Turbo V3 Phone Validator
Checks whether a US phone number is connected or disconnected, and returns its phone type, carrier, subscriber name and subscriber type (consumer or business).
- Wireless ID
Identifies whether a US phone number is a landline or a cell phone, for TCPA compliance.
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 Cliengo
Cliengo to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cliengo to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cliengo to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cliengo to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Cliengo to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cliengo to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Real Phone Validation
Questions
Cliengo and Real Phone Validation, answered
What can start an automation from Cliengo?
Any of Cliengo's 2 triggers in the catalog, including Cliente Nuevo/Actualizado - New/Updated Customer and Nuevo Cliente - New Customer. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Real Phone Validation when something happens in Cliengo?
Any of Real Phone Validation's 9 actions, including Active Phone Check, Do Not Call Lookup, Do Not Call Plus and Scrub Phone Number Validator. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Real Phone Validation to Cliengo?
Real Phone Validation has no triggers in the catalog today, so automations start in Cliengo. If you need the other direction, ask: your agent reads Real Phone Validation's API documentation and adds it.
Do I have to build a connector for Cliengo or Real Phone Validation?
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 Cliengo and Real Phone Validation 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.