Yes. Krokul CRM integrates with Tableau. Krokul publishes its deals, payments, documents and ready reports to your Tableau Cloud or Tableau Server site as Hyper data sources and keeps them current on a schedule. Analysts open them in Tableau like any other published data source, and a failed refresh reported by Tableau turns into a task in Krokul.
Automation platformsZapierMaken8n
You connect Krokul to a Tableau site with a personal access token and pick a project. Krokul builds a Hyper extract for deals, client companies, payments and documents, with the deal ID as the join key, and publishes it as one data source. Workbooks built on it show signed amounts against money received by manager, pipeline and month.
Stage conversion, time on stage, DSO and the ABC and XYZ segments come from the Krokul report engine already calculated. Krokul writes each of them into its own table of the Hyper file. A Tableau dashboard of these tables shows the same figures the Krokul dashboard does.
Once a night Krokul replaces the data in the published data source with a full extract. During the day it appends new payments and closed deals in small Hyper files, so dashboards stay close to what sales sees. Files over the single request limit go up in chunks.
Tableau sends a DatasourceRefreshFailed or WorkbookRefreshFailed webhook when an extract refresh breaks. Krokul creates a task for the person who owns reporting, with the resource name from the payload. The task closes when DatasourceRefreshSucceeded arrives for the same data source.
| Tableau | Direction | Krokul | When |
|---|---|---|---|
| Published data source (.hyper) in a project | Krokul → Tableau | Deals, client companies, contacts, payments, documents | Nightly full replace |
| Extra tables in the same Hyper file | Krokul → Tableau | report/api-conversion, report/api-stageDuration, report/api-dso, report/api-segments | With each publish |
| Append to the published data source | Krokul → Tableau | New payments and won or lost deals | On the intraday schedule |
| Personal access token sign-in | Krokul → Tableau | Krokul connection to the Tableau site | Before each publish |
| Webhook DatasourceRefreshFailed, WorkbookRefreshFailed | Tableau → Krokul | Task for the reporting owner | An extract refresh fails |
| Webhook DatasourceRefreshSucceeded | Tableau → Krokul | The same task closed | The next refresh succeeds |
Yes. Krokul publishes its sales data and reports to Tableau Cloud or Tableau Server as Hyper data sources, and Tableau refresh events come back as tasks. The Krokul app in Zapier, Make and n8n covers flows of your own.
No. The data sources live on your Tableau site, so web authoring and Tableau Desktop both connect to them as published data sources.
No. Tableau reads what Krokul publishes. Changes to deals and payments happen in Krokul, and they reach Tableau with the next publish.
Stage conversion, time on stage, DSO, ABC and XYZ segments, and any custom report built in the Krokul report engine.
The link carries data one way, from Krokul to Tableau. Workbooks, calculations, permissions and sharing of dashboards stay in Tableau, and the published data sources hold what the Krokul key behind the connection is allowed to read.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
Tableau is a trademark of Tableau Software, LLC. Krokul is not affiliated with Tableau.