--- title: "Connect SQL Server and Wachete - APIANT.ai" description: "When \"New or Updated Row\" fires in SQL Server, your agent runs \"Create monitor\" in Wachete." canonical: "https://apiant.ai/connect/sql-server-to-wachete" --- # Connect SQL Server and Wachete When **New or Updated Row** fires in [SQL Server](https://apiant.ai/connections/sql-server), your agent runs **Create monitor** in [Wachete](https://apiant.ai/connections/wachete), or **Any new notification** in Wachete to **Find Row** in SQL Server. Describe the whole flow and it is built, tested on every scenario and kept running. SQL Server **4** triggers SQL Server **7** actions Wachete **2** triggers Wachete **7** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want SQL Server and Wachete to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Wachete watches the pages you care about, and SQL Server holds the records those pages relate to. Joining them means a change notice in Wachete can update or log against the right row in SQL Server, and rows in SQL Server can create or adjust the monitors in Wachete that watch them. The agent builds the connection, tests every scenario and keeps it running. Example flows ## What SQL Server and Wachete can do together ### From SQL Server to Wachete - When **New or Updated Row** in SQL Server then **Create monitor** in Wachete - When **New Row** in SQL Server then **Update monitor** in Wachete ### From Wachete to SQL Server - When **Any new notification** in Wachete then **Find Row** in SQL Server - When **New notification for monitor** in Wachete then **Update Row** in SQL Server 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 Wachete ## Triggers and actions 6 triggers · 14 actions - Trigger **New or Updated Row** Triggers 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 Row** Triggers when you add a new row. - Trigger **New Table** Fires when a new table appears in the connected SQL Server database. - Action **Add Row** Add one row to a table on the connected SQL Server database. - Action **Delete Row** Delete the rows in a table whose chosen column equals a value. - Action **Find Row** Find the first row in a table whose chosen column matches a value. - Action **Find Rows via Custom Query** Runs a SELECT statement you write against the connected SQL Server database and returns every row it matches. - Action **Find Row via Custom Query** Runs a SELECT statement you write against the connected SQL Server database and returns the first row it matches. - Action **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. - Action **Update Row** Change column values on every row of a table whose chosen column matches a value. - Trigger **Any new notification** Fires when there is a new change notification from any monitor in your Wachete account. - Trigger **New notification for monitor** Fires when there is a new change notification from the specified Wachete monitor (taskId). - Action **Create monitor** Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes. - Action **Delete monitor** Delete a Wachete monitor by its ID. - Action **Get monitor** Get information about a specific Wachete monitor by its ID. - Action **Get monitor data** Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range. - Action **List folders** List folder contents, optionally under a parent folder. - Action **List notifications** List change notifications, optionally filtered by monitor (taskId) and date range. - Action **Update monitor** Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record. ## Each app on its own - [ **SQL Server** Connect directly to a Microsoft SQL Server database and run SQL statements from your automations.](https://apiant.ai/connections/sql-server) - [ **Wachete** Wachete monitors web pages (or parts of pages) for changes and notifies you when the text changes or...](https://apiant.ai/connections/wachete) Reviews ## What our customers say ## More from SQL Server - [ **SQL Server to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/sql-server-to-stripe) - [ **SQL Server to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/sql-server-to-trello) - [ **SQL Server to JIRA** Atlassian JIRA Cloud — issue tracking and project management.](https://apiant.ai/connect/sql-server-to-jira) - [ **SQL Server to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/sql-server-to-zoom) - [ **SQL Server to Typeform** Build and publish online forms, surveys, and quizzes with Typeform.](https://apiant.ai/connect/sql-server-to-typeform) - [ **SQL Server to Webflow** Webflow is a professional website builder and CMS for designing, building, and launching responsive...](https://apiant.ai/connect/sql-server-to-webflow) ## More into Wachete - [ **HubSpot to Wachete** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-wachete) - [ **Slack to Wachete** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-wachete) - [ **Mailchimp to Wachete** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-wachete) - [ **Shopify to Wachete** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/shopify-to-wachete) - [ **QuickBooks Online to Wachete** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/quickbooks-online-to-wachete) - [ **Pipedrive to Wachete** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/pipedrive-to-wachete) Questions ## SQL Server and Wachete, answered ### ### Can monitors in Wachete be created from rows already in SQL Server? Yes. A new row in SQL Server, or a row returned by a SELECT statement you write, can trigger the Create monitor action in Wachete using the URL held on that row. The same trigger can also drive Update monitor when the page address or check settings on the row change. ### ### How does a change notice from Wachete reach the right record in SQL Server? The notification carries the monitor ID, so the agent can use Find Row or Find Row via Custom Query in SQL Server to locate the record tied to that monitor. From there it can update that row, add a new row, or run a statement you write. ### ### 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 Wachete when something happens in SQL Server? Any of Wachete's 7 actions, including Create monitor, Update monitor, Get monitor and Get monitor data. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Wachete to SQL Server? Yes. When something happens in Wachete, your agent can act in SQL Server too. This page covers both directions: Wachete's triggers and SQL Server's actions are listed here as well. ### ### Do I have to build a connector for SQL Server or Wachete? 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 SQL Server and Wachete 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.