Store new chat leads in a backend database

When a prospective customer provides details in Cassidy, automatically insert or update a row in SQL Server to retain prospect data.

Try:

See all Cassidy + SQL Server integrations or talk to a human

Trusted by teams already building on Knit·

4.9/5 on G2·

Google for Startups Accelerator

How Knit builds this workflow

The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.

Cassidy Explore Cassidy →

Triggers

New conversation started

Fires when a new chat or conversation begins in Cassidy.

Lead captured in chat

Fires when Cassidy captures a lead during a conversation.

Conversation handed off

Fires when Cassidy escalates a conversation to a human.

Actions

Send a message

Sends a message to a user through Cassidy.

Generate an answer

Asks Cassidy a question against its knowledge base and returns the answer.

Summarize a conversation

Uses Cassidy to summarize a chat transcript.

Create a ticket from a chat

Opens a support ticket from an Cassidy conversation.

SQL Server Explore SQL Server →

Triggers

New row inserted

Fires when a new row is added to a table in SQL Server.

Row updated

Fires when an existing row changes in SQL Server.

Query result ready

Fires when a scheduled query in SQL Server finishes running.

Actions

Run a query

Runs a SQL query against SQL Server and returns the result.

Insert or update a row

Writes a new or updated row to SQL Server.

Sync a table

Syncs a table in SQL Server with data from another source.

Answer chatbot inquiries using database query results When a data query result becomes ready in SQL Server, automatically send a generated message in Cassidy back to the active user. See details

Archive chat summaries upon human agent handoff Whenever a conversation is handed off in Cassidy, automatically write a summary directly into SQL Server for central analytics. See details

See all Cassidy + SQL Server integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Store new chat leads in a backend database” between Cassidy and SQL Server?

Yes — describe it in the box above and Knit's Integrations Agent researches Cassidy and SQL Server's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.

How long does it take to build?

Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.

What is the main benefit of pairing Cassidy with SQL Server?

It bridges public customer chats with backend data stores, ensuring lead details are stored safely and allowing assistants to retrieve live record updates instantly.

Can updates in SQL Server prompt messages in Cassidy?

Yes, when a row is updated or inserted in SQL Server, you can instruct Cassidy to send an automated message or follow-up response to the user.