Integration
Connect SQL Server to LeadExec
When New or Updated Row fires in SQL Server, your agent runs Add order in LeadExec. 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 SQL Server and LeadExec 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 SQL Server can start in LeadExec
When New or Updated Row in SQL Server
then Add order in LeadExec
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 SQL Server and LeadExec
Triggers and actions 4 triggers · 14 actions
- New or Updated Row
Triggers when a new row is added or modified.
- New or Updated Row (Custom Query)
Fires for each new or changed row returned by a SELECT statement you write against the connected SQL Server database.
- New Row
Triggers when you add a new row.
- New Table
Fires when a new table appears in the connected SQL Server database.
- Add Row
Add one row to a table on the connected SQL Server database.
- Delete Row
Delete the rows in a table whose chosen column equals a value.
- Find Row
Find the first row in a table whose chosen column matches a value.
- Find Rows via Custom Query
Runs a SELECT statement you write against the connected SQL Server database and returns every row it matches.
- Find Row via Custom Query
Runs a SELECT statement you write against the connected SQL Server database and returns the first row it matches.
- Run Custom Statement
Runs a statement you write against the connected SQL Server database that changes data rather than returning rows, and reports how many rows it changed.
- Update Row
Change column values on every row of a table whose chosen column matches a value.
- Add client
Creates a new client record in LeadExec, including its client field values.
- Add delivery account
Creates a new delivery account for a LeadExec client, setting its delivery method, price, lead caps, status and offer details.
- Add order
Creates a new lead order for a client, with its start and end dates, renewal option and ordered items.
- List delivery accounts
Returns all delivery accounts for a LeadExec client, including pricing, lead caps, status, criteria and delivery method details.
- List lead types
Returns every lead type set up in your LeadExec account.
- List orders
Returns client orders in LeadExec, optionally narrowed to one order, a client, an order status, or orders starting on or after a date.
- Update client
Updates an existing LeadExec client record, including its status, assignments, portal login and client field values.
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 SQL Server
SQL Server to StripeStripe is a payment processing platform for online businesses.
SQL Server to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
SQL Server to JIRAAtlassian JIRA Cloud — issue tracking and project management.
SQL Server to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
SQL Server to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
SQL Server to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
More into LeadExec
HubSpot to LeadExecHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to LeadExecSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to LeadExecSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to LeadExecGoogle Sheets
Gmail to LeadExecGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LeadExecGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
SQL Server and LeadExec, answered
What can start an automation from SQL Server?
Any of SQL Server's 4 triggers in the catalog, including New or Updated Row, New or Updated Row (Custom Query), New Row and New Table. Describe the moment in plain language and your agent picks the right one.
What can your agent do in LeadExec when something happens in SQL Server?
Any of LeadExec's 7 actions, including Update client, Add client, Add delivery account and Add order. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from LeadExec to SQL Server?
LeadExec has no triggers in the catalog today, so automations start in SQL Server. If you need the other direction, ask: your agent reads LeadExec's API documentation and adds it.
Do I have to build a connector for SQL Server or LeadExec?
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.