Integration
Connect DecisionRules to PhoneVerify
When New Rules fires in DecisionRules, your agent runs Validate Phone Number in PhoneVerify. 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 DecisionRules and PhoneVerify to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 DecisionRules can start in PhoneVerify
When New Rules in DecisionRules
then Validate Phone Number in PhoneVerify
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 DecisionRules and PhoneVerify
Triggers and actions 1 trigger · 11 actions
- New Rules
Fires once for each new rule or rule flow added to the DecisionRules space.
- Add folder
Create a folder under a node.
- Add rule
Create a rule in a space.
- Add rule version
Create a new version of a rule.
- Add tags to rule
Add tags to a rule.
- Delete rule
Delete a rule or rule version.
- Get rule
Gets the latest version of a rule by its ID or alias, regardless of publication status.
- List folders
Get the root folder tree.
- List rules
List rules in a space.
- Update rule
Update a rule version.
- Update rule status
Publish/pending/archive a rule version.
- Validate Phone Number
Verify a UK mobile or landline phone number and return whether it is active, its quality rating, detected number type and normalised form.
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 DecisionRules
DecisionRules to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DecisionRules to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
DecisionRules to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
DecisionRules to Google SheetsGoogle Sheets
DecisionRules to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
DecisionRules to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into PhoneVerify
Questions
DecisionRules and PhoneVerify, answered
What can start an automation from DecisionRules?
Any of DecisionRules's 1 trigger in the catalog, including New Rules. Describe the moment in plain language and your agent picks the right one.
What can your agent do in PhoneVerify when something happens in DecisionRules?
Any of PhoneVerify's 1 action, including Validate Phone Number. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PhoneVerify to DecisionRules?
PhoneVerify has no triggers in the catalog today, so automations start in DecisionRules. If you need the other direction, ask: your agent reads PhoneVerify's API documentation and adds it.
Do I have to build a connector for DecisionRules or PhoneVerify?
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.
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.