- Assets: list and read dashboards, lenses, datasets (with versions) and folders; asset dependencies and scheduled refresh for an asset
- Data preparation: recipes, dataflows and dataflow jobs, replicated datasets, data connectors and connector types (15 routes)
- Query: run SAQL against a dataset version with the /wave/query endpoint — the only write route in the set
- Governance: templates, security predicates, actions on an entity and instance limits
- 37 routes (36 read-only) under /services/data/v{version}/wave, documented in the AI integration guide (llms.txt)
Salesforce CRM Analytics Connect API Connector
Salesforce CRM Analytics (formerly Tableau CRM / Einstein Analytics) Connect REST API under /wave — dashboards, lenses, datasets and their versions, recipes, dataflows and dataflow jobs, replicated datasets, data connectors and connector types, templates, folders, security, dependencies, actions and the SAQL query endpoint — registered in Apivom Atlas as 37 routes on your My Domain org.
What you can do
Use cases
- Dataset refresh orchestration — List dataflow and recipe jobs, start the next run when upstream loads finish and alert when a job fails — from your own scheduler.
- KPIs from SAQL in other tools — Run SAQL against a dataset version and surface the result in a portal, a chat assistant or a report outside Salesforce.
- Asset inventory and governance — Catalogue dashboards, lenses, their dependencies and security predicates across orgs for review and clean-up.
CRM Analytics is the analytics layer that lives inside Salesforce: datasets built from CRM and external data through dataflows and recipes, lenses and dashboards on top of them, and SAQL — the Salesforce Analytics Query Language — to query a dataset directly. Its Connect REST API exposes all of that under /wave, and Apivom Atlas registers 37 of those routes, 36 of them read-only: the asset catalogue (dashboards, lenses, datasets and versions, folders, templates), the data-preparation objects (recipes, dataflows and their jobs, replicated datasets, data connectors) and the single query route that executes SAQL. The credential contract is a Connected App on your My Domain org. No Apivom product workflow uses CRM Analytics today — Apivom's own analytics reads Apivom tenant data, not CRM Analytics datasets — so the connector is catalogued for customers who already have dashboards and datasets in CRM Analytics and want an Apivom product to read or trigger them, scoped per customer.
A Connected App on your Salesforce org (consumer key + secret) and your My Domain instance URL. The caller runs the OAuth 2.0 flow and sends the access token as Bearer; the instance URL becomes the per-request base URL. Apivom Atlas forwards, logs and stores nothing.
Frequently asked questions
Can I switch this connector on today?
The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.
Is this Tableau?
No. CRM Analytics is the analytics product embedded in the Salesforce platform (formerly Tableau CRM / Einstein Analytics). Tableau Server and Tableau Cloud have a separate REST API and their own connector in this catalogue.
Does any Apivom product read CRM Analytics datasets?
No. Apivom's analytics work on data held in your Apivom tenant. This connector is registered so a customer's CRM Analytics assets could be read or refreshed from an Apivom workflow if scoped; nothing of the kind runs today.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.