Integration
Connect Intervals and SQL Server
When New client fires in Intervals, your agent runs Add Row in SQL Server, or New or Updated Row in SQL Server to Add invoice in Intervals. 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 Intervals and SQL Server 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)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 Intervals and SQL Server can do together
From Intervals to SQL Server
When New client in Intervals
then Add Row in SQL Server
When New invoice in Intervals
then Update Row in SQL Server
From SQL Server to Intervals
When New or Updated Row in SQL Server
then Add invoice in Intervals
When New Row in SQL Server
then Add task in Intervals
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 Intervals and SQL Server
Triggers and actions 10 triggers · 45 actions
Trigger
New clientPolling trigger: fires when a new client is created in Intervals.
Trigger
New invoicePolling trigger: fires when a new invoice is created in Intervals.
Trigger
New milestonePolling trigger: fires when a new milestone is created in Intervals.
Trigger
New personPolling trigger: fires when a new person is added in Intervals.
Trigger
New projectPolling trigger: fires when a new project is created in Intervals.
Trigger
New taskPolling trigger: fires when a new task is created in Intervals.
Action
Add clientCreate a new client.
Action
Add expenseCreate a new expense.
Action
Add invoiceCreate a new invoice.
Action
Add milestoneCreate a new milestone.
Action
Add personCreate a new person (team member).
Action
Add projectCreate a new project.
Action
Add taskCreate a new task.
Action
Add time entryLog a new time entry against a task.
Action
Add timerStart a new timer for a task.
Action
Delete clientDelete a client.
Action
Delete expenseDelete an expense.
Action
Delete invoiceDelete an invoice.
Action
Delete milestoneDelete a milestone.
Action
Delete personDelete a person.
Action
Delete projectDelete a project.
Action
Delete taskDelete a task.
Action
Delete time entryDelete a logged time entry.
Action
Delete timerDelete a timer.
Action
Get clientRetrieve a single client by id.
Action
Get expenseRetrieve a single expense by id.
Action
Get invoiceRetrieve a single invoice by id.
Action
Get milestoneRetrieve a single milestone by id.
Action
Get personRetrieve a single person by id.
Action
Get projectRetrieve a single project by id.
Action
Get taskRetrieve a single task by id.
Action
Get time entryRetrieve a single logged time entry by id.
Action
Get timerRetrieve a single timer by id.
Action
List milestonesRetrieve all milestones in the Intervals account.
Action
List tasksRetrieve all tasks in the Intervals account.
Action
Update clientUpdate an existing client's details.
Action
Update expenseUpdate an existing expense.
Action
Update invoiceUpdate an existing invoice.
Action
Update milestoneUpdate an existing milestone.
Action
Update personUpdate an existing person's details.
Action
Update projectUpdate an existing project's details.
Action
Update taskUpdate an existing task's details.
Action
Update time entryUpdate an existing logged time entry.
Action
Update timerUpdate a timer (e.g. stop or adjust it).
Trigger
New or Updated RowTriggers when a new row is added or modified.
Trigger
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.
Trigger
New RowTriggers when you add a new row.
Trigger
New TableFires when a new table appears in the connected SQL Server database.
Action
Add RowAdd one row to a table on the connected SQL Server database.
Action
Delete RowDelete the rows in a table whose chosen column equals a value.
Action
Find RowFind the first row in a table whose chosen column matches a value.
Action
Find Rows via Custom QueryRuns a SELECT statement you write against the connected SQL Server database and returns every row it matches.
Action
Find Row via Custom QueryRuns a SELECT statement you write against the connected SQL Server database and returns the first row it matches.
Action
Run Custom StatementRuns a statement you write against the connected SQL Server database that changes data rather than returning rows, and reports how many rows it changed.
Action
Update RowChange column values on every row of a table whose chosen column matches a value.
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 Intervals
Intervals to AsanaAsana is a collaborative information manager for workspace.
Intervals to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Intervals to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Intervals to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Intervals to MailchimpMailchimp marketing automation and email platform.
Intervals to StripeStripe is a payment processing platform for online businesses.
More into SQL Server
HubSpot to SQL ServerHubSpot is your all-in-one stop for all of your marketing software needs.
Slack to SQL ServerSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mailchimp to SQL ServerMailchimp marketing automation and email platform.
Shopify to SQL ServerShopify is a commerce platform for online stores and retail point-of-sale.
QuickBooks Online to SQL ServerQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pipedrive to SQL ServerPipedrive is a sales CRM and pipeline management tool.
Questions
Intervals and SQL Server, answered
What can start an automation from Intervals?
Any of Intervals's 6 triggers in the catalog, including New client, New invoice, New milestone and New person. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SQL Server when something happens in Intervals?
Any of SQL Server's 7 actions, including Update Row, Add Row, Find Row and Find Rows via Custom Query. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SQL Server to Intervals?
Yes. When something happens in SQL Server, your agent can act in Intervals too. This page covers both directions: SQL Server's triggers and Intervals's actions are listed here as well.
Do I have to build a connector for Intervals or SQL Server?
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 Intervals and SQL Server 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.