- Platform
- Preview
- Labs
How to read Platform results: this is the bedrock.
New
Salesforce is fully supported
Salesforce is fully supported
- The Salesforce connector is now production-ready, covering the core objects most teams rely on — users, accounts, opportunities, contracts, tasks, and more.
- Syncs run incrementally with cursor-based pagination, so large orgs don’t re-pull everything on every sync.
- If you asked us for Salesforce and were on the waitlist, reach out to your Parable team — we can enable it for your workspace.
You'll hear about broken connectors immediately
You'll hear about broken connectors immediately
- When a connector transitions from healthy to a problem state — expired credentials, failed syncs, invalid config — the integrator owners on your team now receive an email and a Slack notification automatically.
- No more finding out at your next dashboard review; the right person hears about it as soon as it happens.
Large credentials (like Google service account keys) now work end-to-end
Large credentials (like Google service account keys) now work end-to-end
- Some integrations — most notably Google Workspace service account keys — rely on credentials that are too large for classic single-pass encryption.
- Parable now uses a layered encryption approach that removes that size limit entirely, so these credentials are handled cleanly during setup.
- You shouldn’t notice anything different during connector setup — it just stops being an edge case.
Admins can mark connectors as Required or Suggested
Admins can mark connectors as Required or Suggested
- Your Parable team can now indicate which connectors matter most for your workspace — Required (we need this to get you value) or Suggested (nice to have).
- You’ll see the priority in the connector directory, so setup feels like a checklist instead of a menu.
Improved
Clearer messages when a credential issue happens
Clearer messages when a credential issue happens
- Credential-related errors used to come in four flavors that sometimes pointed in the wrong direction (for example, asking you to fix your credentials when the issue was on our side).
- Now there’s one clean Credential issue state with the specific reason shown on demand, a separate Config issue state for configuration mismatches, and a new Internal issue state for the rare cases where the fault is ours — so you never see “please reconnect” when reconnecting wouldn’t help.
Data freshness checks understand your pipeline shape
Data freshness checks understand your pipeline shape
- Parable’s “is this data current?” guard now knows the difference between connectors that refresh everything on every sync and connectors that load incrementally.
- Practical effect: fewer false “this looks stale” flags on datasets that were always fine — especially for incremental loads that were being compared against the wrong benchmark.
Google Workspace service-account keys are more forgiving
Google Workspace service-account keys are more forgiving
- If a pasted Google service account key contained escaped newline characters (common when credentials round-trip through a text editor), setup used to fail with an opaque error.
- Parable now normalizes that automatically — the credential just works.
GitLab user sync stays inside your organization
GitLab user sync stays inside your organization
- Connecting GitLab used to trigger an extra-long first sync on large instances, because we were pulling every visible user across the platform, not just your team.
- Defaults now scope user ingestion to members of your groups — meaningfully shorter first sync for GitLab workspaces of any size.
Small UI polish across the connector experience
Small UI polish across the connector experience
- Connector schedules no longer show a “next run” in the past on freshly-reconfigured integrations.
- Breadcrumb paths with accidental duplicates (e.g. “Jira → Jira”) are deduplicated.
- Redundant timestamp clutter on connection cards removed.
Fixed
A batch of data-pipeline quality fixes
A batch of data-pipeline quality fixes
- Several underlying fixes to keep data flowing cleanly after our recent connector-metadata update — primarily for workspaces using Zoom, Salesforce, and Google Workspace integrations.
- If you were seeing intermittent issues on any of those, you should see them resolved.
Form state resets cleanly when you close a setup dialog
Form state resets cleanly when you close a setup dialog
- A small but noticeable quality-of-life fix — closing and re-opening a connector setup flow no longer carries over stale form values from the previous attempt.