Integration
Connect Noko to Azure Sql
When Entry Changed fires in Noko, your agent runs Get SQL Database in Azure Sql. 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 Noko and Azure Sql 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 Noko can start in Azure Sql
When Entry Changed in Noko
then Get SQL Database in Azure Sql
When Invoice Changed in Noko
then Get SQL Server in Azure Sql
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 Noko and Azure Sql
Triggers and actions 6 triggers · 18 actions
Trigger
Entry ChangedTriggers when a Noko time entry is created or changed.
Trigger
Invoice ChangedTriggers when a Noko invoice is created or changed.
Trigger
New EntryTriggers when a new time entry is logged in Noko.
Trigger
New ExpenseTriggers when a new expense is logged in Noko.
Trigger
New InvoiceTriggers when a new invoice is created in Noko.
Trigger
New ProjectTriggers when a new project is created in Noko.
Action
Approve EntryMarks a Noko time entry as approved.
Action
Archive ProjectArchives a Noko project.
Action
Create EntryLogs a new time entry in Noko.
Action
Create ExpenseLogs a new expense against a Noko project.
Action
Create ProjectCreates a new Noko project.
Action
Create TagsCreates one or more Noko tags.
Action
Delete EntryDeletes a Noko time entry.
Action
Find ExpenseFinds the most recent Noko expense matching the filters.
Action
Find InvoiceFinds a Noko invoice by reference, state or company.
Action
Find ProjectFinds a Noko project by name.
Action
Find UserFinds a Noko user by name or email.
Action
Get EntryReturns a single Noko time entry by its ID.
Action
Mark Invoice as PaidMarks a Noko invoice as paid.
Action
Update EntryUpdates a Noko time entry's date, minutes, description, project or user.
Action
Get SQL DatabaseFetches one Azure SQL database by name, including its status, tier and size limit. An error occurs if the database is not found.
Action
Get SQL ServerFetches one Azure SQL logical server by name, including its region, admin login, host name and network settings. An error occurs if the server is not found.
Action
List SQL DatabasesReturns the databases on an Azure SQL server, with each database's name, status, tier and size limit.
Action
List SQL ServersReturns the Azure SQL logical servers in a subscription, with each server's name, region, admin login and host name.
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 Noko
Noko to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Noko to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Noko to StripeStripe is a payment processing platform for online businesses.
Noko to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Noko to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Noko to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Azure Sql
ComplyCube to Azure SqlComplyCube is an all-in-one identity verification, KYC and anti-money laundering compliance platform for...
CRUSH to Azure SqlCRUSH is an AI powered second brain helping you collect a thought, organize it and take action.
HubSpot to Azure SqlHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Azure SqlSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Azure SqlSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Azure SqlGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Questions
Noko and Azure Sql, answered
What can start an automation from Noko?
Any of Noko's 6 triggers in the catalog, including Entry Changed, Invoice Changed, New Entry and New Expense. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Azure Sql when something happens in Noko?
Any of Azure Sql's 4 actions, including Get SQL Database, Get SQL Server, List SQL Databases and List SQL Servers. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Azure Sql to Noko?
Azure Sql has no triggers in the catalog today, so automations start in Noko. If you need the other direction, ask: your agent reads Azure Sql's API documentation and adds it.
Do I have to build a connector for Noko or Azure Sql?
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 Noko and Azure Sql 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.