tableau-salesforce-connector
Tableau ↔ Salesforce integration patterns: Tableau Salesforce connector, Tableau for Salesforce, CRM Analytics alternative, Data Cloud + Tableau, embedded Tableau dashboards. Choose between connector modes (live, extract, direct-to-Data-Cloud). NOT for CRM Analytics Studio (use crm-analytics-foundation). NOT for generic Tableau Server setup.
Best use case
tableau-salesforce-connector is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Tableau ↔ Salesforce integration patterns: Tableau Salesforce connector, Tableau for Salesforce, CRM Analytics alternative, Data Cloud + Tableau, embedded Tableau dashboards. Choose between connector modes (live, extract, direct-to-Data-Cloud). NOT for CRM Analytics Studio (use crm-analytics-foundation). NOT for generic Tableau Server setup.
Teams using tableau-salesforce-connector should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/tableau-salesforce-connector/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How tableau-salesforce-connector Compares
| Feature / Agent | tableau-salesforce-connector | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Tableau ↔ Salesforce integration patterns: Tableau Salesforce connector, Tableau for Salesforce, CRM Analytics alternative, Data Cloud + Tableau, embedded Tableau dashboards. Choose between connector modes (live, extract, direct-to-Data-Cloud). NOT for CRM Analytics Studio (use crm-analytics-foundation). NOT for generic Tableau Server setup.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Tableau ↔ Salesforce Connector Activate when integrating Tableau (Cloud, Server, or Tableau for Salesforce) with Salesforce for reporting and dashboards. The connector has several modes with very different API-limit, freshness, and cost implications; choosing the wrong mode is a frequent source of silent throttling and stale dashboards. ## Before Starting - **Distinguish Tableau for Salesforce from vanilla Tableau.** Tableau for Salesforce is a specific SKU with native record-page embedding (Tableau Viz LWC). Vanilla Tableau Cloud needs Connected App + iframe. - **Measure the reporting surface.** A single executive dashboard refreshed daily is different from 50 operational dashboards with hourly refreshes. API budget is the governor. - **Decide on governance.** Data Cloud + Tableau centralizes governance; raw Salesforce connector gives freshness but each dashboard is a bespoke SOQL payload. ## Core Concepts ### Connector modes - **Live connection** — Tableau queries Salesforce via REST/SOQL on every view. Fresh but API-expensive. - **Extract** — Tableau pulls periodically into a data extract (TDE / Hyper). Fast for users, older data, explicit refresh schedule. - **Data Cloud → Tableau** — Data Cloud ingests Salesforce + other sources, Tableau queries Data Cloud's Hyper DB via Zero Copy. ### Tableau for Salesforce embedding Tableau Viz LWC renders a Tableau dashboard on a Salesforce record page with context passing (e.g., AccountId to dashboard filter). Works with Tableau Cloud and Tableau Server. Requires Connected App setup. ### API limits Live connections consume API calls and SOQL governor limits. A dashboard with many worksheets hits the API for each. Budget matters. ### Row-level security Tableau RLS via user filters or Data Cloud sharing → differs from Salesforce sharing. Match Tableau security to Salesforce intent (or use CRM Analytics which inherits sharing natively). ## Common Patterns ### Pattern: Executive dashboards — extract-based Daily extract of a curated dataset. Dashboards serve from the extract — fast, predictable, no API pressure. Refresh in off-hours. ### Pattern: Operational dashboards on record pages — Tableau for Salesforce + live Tableau Viz LWC on Account page with live connection filtered by AccountId. User sees current data; API cost scoped to the single context. ### Pattern: Cross-source analytics — Data Cloud + Tableau Zero Copy Data Cloud ingests Salesforce, marketing, external data. Tableau queries Data Cloud via Zero Copy. Centralized governance; decoupled from Salesforce API limits. ### Pattern: Hybrid — extract for base, live for drill Base dashboard uses extract (speed). Drill-through opens a live-connected view (freshness on demand). Optimizes for most users while preserving on-demand freshness. ## Decision Guidance | Scenario | Recommended Mode | Reason | |---|---|---| | Executive daily dashboard | Extract | API-light, user-fast | | Embedded record page dashboard | Live + Tableau for Salesforce | Contextual freshness | | Cross-source analytics | Data Cloud + Tableau | Governance, scale | | Salesforce sharing fidelity required | CRM Analytics (alternative) | Native inheritance | | High-volume operational (50+ live dashboards) | Data Cloud intermediary | Avoid API ceiling | ## Recommended Workflow 1. Classify each dashboard: audience, refresh cadence, embedding context. 2. Forecast API consumption per dashboard in live mode; compare against org API limit. 3. Choose connector mode per dashboard (not org-wide — it is per-workbook). 4. Configure Tableau Connected App + OAuth; set up Tableau for Salesforce if using Tableau Viz LWC. 5. Build one dashboard end-to-end; validate embedding, filters, security. 6. Establish extract refresh schedule; monitor refresh duration and failure rate. 7. Document governance: who publishes, who sees what, how row-level security is enforced. ## Review Checklist - [ ] Per-dashboard mode decision documented - [ ] API forecast within org limits with headroom - [ ] Tableau Connected App + OAuth configured - [ ] Tableau Viz LWC components tested on record pages - [ ] Row-level security validated against Salesforce sharing intent - [ ] Extract refresh monitoring in place - [ ] Rollback plan if a dashboard causes API throttling ## Salesforce-Specific Gotchas 1. **Tableau live queries run SOQL that can exceed selectivity requirements.** Non-selective queries fail in large orgs regardless of API budget. 2. **Tableau Connected App uses OAuth 2.0; lifetime tokens must be scoped.** Over-scoped tokens expose data beyond the dashboard's purpose. 3. **Tableau for Salesforce uses cross-domain iframe — CSP and CORS matter.** Misconfiguration silently blanks the viz without surface errors. ## Output Artifacts | Artifact | Description | |---|---| | Dashboard inventory with mode | Per dashboard: live / extract / Data Cloud | | API consumption forecast | SOQL + REST call estimate | | Embedding architecture | Tableau Viz LWC setup, CSP changes | | RLS mapping | Salesforce sharing → Tableau user filters | ## Related Skills - `data/data-cloud-foundation` — Data Cloud as analytical source - `integration/integration-pattern-selection` — adjacent integration choices - `data/crm-analytics-foundation` — alternative analytics path
Related Skills
salesforce-shield-deployment
Roll out Shield (Platform Encryption + Event Monitoring + Field Audit Trail) end-to-end, sequencing feature enablement to avoid data lockout. NOT for Classic Encryption or general PE design.
ferpa-compliance-in-salesforce
Use this skill when implementing FERPA (Family Educational Rights and Privacy Act) compliance controls in Salesforce Education Cloud or Education Data Architecture (EDA): LearnerProfile FERPA boolean fields, directory information opt-out via FLS and Individual data privacy flags, ContactPointTypeConsent for parental and third-party disclosure, 45-day student records response window tracking, and consent workflow automation. Trigger keywords: FERPA, student records privacy, LearnerProfile, parental disclosure, directory information opt-out, education data privacy, student consent, education cloud compliance. NOT for GDPR/CCPA general data privacy (see gdpr-data-privacy skill), platform encryption at rest (see platform-encryption skill), or HIPAA health-data compliance.
industries-cpq-vs-salesforce-cpq
Use this skill when comparing Industries CPQ (formerly Vlocity CPQ) with Salesforce CPQ (Revenue Cloud managed package) — covering feature parity, decision criteria, migration paths, and coexistence patterns. Trigger keywords: Vlocity CPQ, Industries CPQ, Salesforce CPQ comparison, Revenue Cloud migration, CPQ selection, which CPQ to use. NOT for implementing, configuring, or debugging either CPQ product.
tableau-embedding-in-lightning
Embedding Tableau dashboards (and Tableau Pulse insights) inside Lightning App / Record / Home pages — Tableau Embedding API v3 in an LWC, the connected-app + JWT trust pattern for SSO from Salesforce to Tableau, row-level security so a Salesforce user only sees their data in Tableau, CSP / Trusted Sites configuration for the Tableau host, and the Tableau Viz Lightning Web Component (drag-and-drop alternative to a custom LWC). NOT for building Tableau dashboards / data sources (that's Tableau-side work), NOT for CRM Analytics (Tableau is the separate product; see data/crm-analytics-patterns).
slack-salesforce-integration-setup
Use this skill when setting up or troubleshooting the Salesforce for Slack managed app — including connecting a Salesforce org to a Slack workspace, configuring the three-party admin handshake, linking Slack channels to Salesforce records, enabling record preview sharing, and managing org-level limits. Triggers on: Salesforce for Slack app not connecting, Slack org connection setup, Salesforce record sharing in Slack, Slack workspace admin approval, connecting Salesforce to Slack. NOT for building custom Slack apps or Slack bots (separate development platform), not for Slack Workflow Builder Salesforce connector (use slack-workflow-builder skill), not for Flow-based Slack messaging (use flow-for-slack skill).
salesforce-to-salesforce-integration
Use this skill to implement Salesforce-to-Salesforce integration patterns — covering the native S2S feature, API-based cross-org sync, Platform Event bridging, and Salesforce Connect Cross-Org adapter. Trigger keywords: Salesforce to Salesforce integration, cross-org data sharing, S2S feature, cross-org Platform Events, Salesforce Connect cross-org. NOT for multi-org strategy or architecture decisions (use architect/multi-org-strategy), single-org data sharing, or external (non-Salesforce) system integration.
salesforce-maps-setup
Use when configuring Salesforce Maps (formerly MapAnything) — territory planning, route optimization, live tracking, geo-grid visualizations, and check-in/check-out workflows for Sales or Service field reps not on Field Service. Covers package installation order (Maps + Maps Advanced + Maps Routing/Live Tracking add-ons), the MapsTerritoryPlan / MapsAdvancedRoute / MapsLayer object family, base-data syncs (Geocoding and Routing services), and integration with Sales and Service Cloud records. Triggers: 'Salesforce Maps setup', 'MapAnything migration', 'territory planning by polygon', 'route optimization for sales reps', 'live tracking field reps', 'plot accounts on a map', 'check-in to the closest account'. NOT for Field Service Lightning territory and scheduling (use admin/fsl-scheduling-optimization-design and data/fsl-territory-data-setup) — Maps and FSL are different products. NOT for Consumer Goods Cloud retail visit planning (use admin/consumer-goods-cloud-setup) — RoutePlan/Visit objects are CG-specific. NOT for Tableau / CRM Analytics geo charts.
salesforce-functions-replacement
Salesforce Functions is retired (EOL Jan 2025). This skill maps Functions workloads to replacements: Heroku (with Hyperforce), external containers, Apex (where viable), Agentforce Actions, external compute via Named Credentials. NOT for Lambda / Azure Functions tutorials. NOT for Apex @future replacement (use async-selection tree).
salesforce-data-pipeline-etl
Export large Salesforce datasets to a lakehouse via Bulk API 2.0, CDC streams, or Salesforce Data Pipelines. NOT for ad-hoc exports.
salesforce-connect-external-objects
Use when deciding whether Salesforce Connect and External Objects are the right fit for external data access, or when reviewing OData, cross-org, and custom adapter patterns, query limitations, and latency tradeoffs. Triggers: 'Salesforce Connect', 'External Objects', '__x', 'OData adapter', 'custom adapter'. NOT for ordinary ETL or replicated-data designs where the data should live inside Salesforce.
outbound-webhook-from-salesforce
Use when Salesforce must POST a webhook to a third-party endpoint after a record change — with signed payloads, retries, dead-lettering, rate limits, and idempotency. Covers design choice between Outbound Message, Flow HTTP Callout, Apex Queueable callout, and Event Relay. Does NOT cover inbound webhooks into Salesforce (see inbound-webhook or apex-rest-webhook).
mulesoft-salesforce-connector
Designing and configuring MuleSoft Anypoint Salesforce Connector flows: API selection (SOAP/REST/Bulk/Streaming), OAuth 2.0 JWT Bearer auth, watermark-based incremental sync with Object Store, batch processing with record-level error isolation, and replay topic subscriptions. Use when building Mule 4 flows that read from or write to Salesforce, migrating from Mule 3 watermark to Mule 4 Object Store, or troubleshooting connector authentication and API limits. NOT for native Salesforce-to-Salesforce integration without MuleSoft (use platform-events-integration or change-data-capture-integration). NOT for generic REST callout patterns from Apex (use rest-api-patterns).