Connect Databricks, and Simplesat copies your survey responses into a table in the catalog and schema you choose. It then keeps the table current for the surveys and sentiments you pick.

The integration is available on every Simplesat plan. To connect it and switch it on, you need the Manage integrations permission, which Owner and Admin have by default.

In Databricks, you need:

The service principal needs:

Integration security, permissions and data flow covers what a connected tool can read and write.

Start in Databricks, where you create the secret and find the warehouse ID:

Then, in Simplesat:

The table is a Delta table. It's created when the first response reaches the integration after you activate it. Then every existing response in your workspace is copied in, from every survey, whatever you chose under When should this integration run?. With a lot of history, that takes a while. After that, only responses from the surveys and sentiments you chose are added.

If you change Table to a name that doesn't exist yet, the next response creates that table and copies every response into it.

Each response has one row, matched on id. A new response adds a row, and a response that changes has its row updated, for example when the customer answers another question later or someone edits a rating.

The integration gets a response no sooner than five minutes after it arrives, and again whenever it changes. Only active responses are sent, not withheld, hidden or spam ones.

Tagging a response in Simplesat doesn't update its row, so the tag reaches Databricks only when the response itself next changes.

What answers and tags hold depends on how a row was written:

A Databricks OAuth secret lasts 730 days at most. When it expires or is deleted, every sync fails, while the Databricks page still shows Authenticated with Databricks. Replace it before then:

To connect a different workspace or service principal, follow the same steps with its details.

Start with the secret. If it expired or was deleted, every sync fails while the page still shows Authenticated with Databricks. Generate a new secret, then click Revoke access, Authenticate with the new secret, and click Activate integration. If the secret is fine, check that the SQL warehouse still exists and that the service principal still has its permissions. If none of that explains it, contact us. Responses that arrived while syncs were failing aren't added later.

The table appears with the first response that reaches the integration after you activate it, at least five minutes after that response arrives. If a response has come in since then, check that:

Rows copied in when the table is created hold every answer until their response changes and the row is rewritten. Rows written as responses arrive hold only the answer to the question your metric rating comes from. team_members is always empty.

Tagging a response doesn't update its row, so the tag reaches Databricks only when the response itself next changes. Rows copied in when the table is created hold the customer's tags in tags, not the response's.

No. The integration connects only to workspaces on Databricks on AWS, whose address ends in .cloud.databricks.com. To get your responses into another workspace, export them as a CSV from Feedback, or read them through the Simplesat API.

It creates the table if it doesn't exist. The catalog, the schema and the SQL warehouse have to exist already.

In Databricks SQL, put a colon after the column name. For example, customer:email returns the customer's email, and survey:name returns the survey's name. To cast a value, add ::, for example ::int.

Every existing response in your workspace, from every survey. After that, only responses from the surveys and sentiments you chose are added or updated.