Documentation Index
Fetch the complete documentation index at: https://rollout.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Release window: April 23, 2026 - May 15, 2026
New
- Added Follow Up Boss OAuth credential support, so tenants can connect Follow Up Boss accounts with OAuth while API-key authentication remains available.
- Added expanded Follow Up Boss webhook ingestion for appointments, calls, events, notes, people, relationships, stages, tasks, text messages, and pipelines, so provider-originated changes update more Universal API records.
- Added Zipform connector support for people, transactions, and documents, so Zipform data can be synced through the Universal API connector surface.
Improved
- Improved Zipform sync reliability for people, transactions, and documents, so Zipform imports handle larger datasets and optional document sync more consistently.
- Added configurable auth-plan selection in the Dashboard Credentials Manager, so dashboard-created credentials can use non-default auth plans when a connector exposes multiple authentication methods.
- Improved inbound sync callbacks to fire after the first successful sync and after repeated sync failures, so tenant systems can react to credential readiness and credential errors.
- Improved outbound webhook handling by disabling endpoints after repeated failed deliveries and deleting old webhook events after 14 days, so unhealthy endpoints stop accumulating retries.
- Improved large-record sync behavior for Follow Up Boss, BoldTrail, Lofty, and Encompass, so high-volume credentials are less likely to fail from buffering, rate-limit, or end-of-list edge cases.
- Improved connector file upload handling by retrying unexpected uploader responses and preserving structured response details, so file and document sync failures are easier to recover and diagnose.
Fixed
- Fixed Zipform transaction parsing when property address or data fields are null, so partial transaction records no longer fail sync.
- Fixed Lofty parsing for nullable task assignees, appointment descriptions, call phone numbers, and failed call recording uploads, so partial Lofty activity data syncs instead of crashing.
- Fixed Lofty appointment create, update, delete, custom-stage, and call-sync handling, so Lofty activity and appointment workflows produce more stable Universal API records.
- Fixed Dotloop requests to refresh tokens once after a 401 before invalidating credentials, so transient token expiry is less likely to break Dotloop people and transaction operations.
- Fixed Follow Up Boss schema and mapping issues for stages, people, saved properties, and listings, so synced records avoid validation and mapping failures.
- Fixed Sierra Interactive and Encompass sync edge cases, so invalid Sierra credentials surface correctly and Encompass user sync can finish cleanly at the end of paginated results.
Action required
- To use Follow Up Boss OAuth, configure the Follow Up Boss OAuth client settings and whitelabeled return URI before selecting the OAuth auth plan.
Release window: April 9 - April 22, 2026
New
- Added the Mortgage CRM API category with Jungo and Salesforce-backed connectors for people and notes, so integrators can manage mortgage CRM contacts and notes through a dedicated API surface.
- Added Brivity CRM sync coverage for appointments, calls, events, and notes, so Brivity credentials expose more activity history through the CRM API.
- Added Wise Agent support for notes CRUD, appointments, calls, TMS transactions, events, and properties, so Wise Agent integrations can cover contact activity plus transaction and property workflows.
- Added Lofty people relationship sync, so relationship records attached to leads can be returned through the Universal API people relationships entity.
- Added credential error callback configuration, so tenants can receive signed notifications when a credential fails sync or transform attempts.
Improved
- Moved person custom fields into the
customFieldsobject, so custom metadata is returned in a consistent shape across connectors instead of connector-specific top-level keys. - Improved BoldTrail sync resilience by checking connector capabilities before optional activity endpoints, so limited credentials can skip unsupported entities instead of failing the whole sync.
- Improved outbound DB sync to resync rows when a credential’s consumer keys change, so external tables keep
consumerKeyscurrent. - Reduced default background polling and sync frequency for selected connectors, so credentials that are not intended for frequent background sync place less load on provider APIs.
Fixed
- Fixed Lofty event and task writes for scheduled dates, property details, post-create activity visibility, and task deletion, so CRM activity writes produce stable source records.
- Fixed Sierra Interactive person assignment handling, so
assignedUserIdchanges on create and update are sent to Sierra correctly. - Fixed iCloud Contacts credential setup, so users no longer need to enter a CardDAV base URL when connecting iCloud Contacts.
- Fixed HighLevel event creation to include a note title, so created events do not appear as blank notes in HighLevel.
- Fixed Open To Close contact ingestion for nullable first names and empty contact roles, so partial contact records no longer fail sync.
Action required
- If you read or write person custom fields as top-level
customFooproperties, update your integration to use thecustomFieldsobject. - If you want credential-error notifications, configure the credential errored callback URL in Dashboard Settings and verify
X-Rollout-Signaturewith your tenant client secret.
Release window: April 2 - April 8, 2026
New
- Added
@rollout/link-react0.16.0 hooks for pre-add and pre-delete credential checks, so embedded auth flows can enforce custom validation or confirmation before mutating credentials.
Improved
- Improved dashboard credential settings by fixing
entitiesToSyncpersistence, so entity-level sync selections now save correctly and trigger a clean resync. - Improved credential refresh reliability by serializing refresh work with a global per-credential lock, so concurrent requests are less likely to trigger duplicate refresh attempts.
- Improved Lofty sync throughput by streaming per-lead records as they are fetched and capping concurrency, which reduces buffering pressure on large imports.
Fixed
- Fixed SkySlope transaction original-data output to include link fields, so downstream consumers receive source URLs alongside transaction records.
- Fixed Google Contacts and iCloud Contacts timezone normalization to emit
nullinstead of empty strings, which prevents blank timezone values from being mistaken for real data. - Fixed Lofty auth failure handling to invalidate credentials when the API reports
User in token does not exist, which surfaces broken tokens earlier.
Action required
- No action required for existing integrations.
Release window: March 19 - April 1, 2026
New
- Added person
timezonesupport to Universal API create and output models plus connector transforms, so integrations can store and round-trip timezone metadata on contacts. - Added HighLevel event support by creating CRM events as prefixed contact notes and transforming those notes back into Universal API events, so activity writes and reads stay aligned in HighLevel.
- Added iCloud Contacts connector support with CardDAV authentication and incremental people sync, so Apple contacts can now be imported through the Universal API.
- Added HubSpot stages support and stage-aware people writes via
hs_lead_status, so integrations can sync valid stage catalogs and update lead status without custom mapping. - Added Lofty sources support and agent reassignment through Lofty’s assignment endpoint, so integrations can sync source catalogs and reassign leads more reliably.
Improved
- Improved Lofty call sync by switching to official call and recording endpoints, which removes the browser-dependent path and reduces import fragility.
- Improved Google Contacts auth labeling by restoring user info scopes and email-based credential labels, so dashboards and embedded UIs identify credentials by account email again.
- Improved Encompass sync stability by cutting loan and user fetch batch sizes to 10, which reduces provider-side batch failures on large syncs.
Fixed
- Fixed Sierra Interactive entity sync coverage so appointments and calls are fetched correctly under the connector’s conditional entity flow.
Action required
- No action required for existing integrations.
Release window: March 5 - March 18, 2026
New
- Added CRM offices endpoints for connectors that expose offices, including HighLevel, so integrators can read and write office records through the CRM API.
Improved
- Improved Sierra Interactive sync reliability under provider throttling by adding shared API rate limiting, bounded webhook waits, and safer lead-fetch concurrency.
- Improved BoldTrail sync compatibility across plans by probing enrichment capabilities once per run and skipping advanced-only enrichment calls for non-advanced credentials.
- Improved Skyslope user sync scoping by filtering users to the credential’s office GUIDs, which keeps imported users aligned with accessible offices.
Fixed
- Fixed
@rollout/link-reactOAuth popup handling so browser auth windows open reliably before the authorize URL request completes. - Fixed Lofty credential setup to validate the supplied secret against the current API auth flow and accept direct token-style credentials when they are valid.
- Fixed HighLevel person writes to fall back to the credential location and reuse existing contact IDs on duplicate creates, which reduces failed writes and duplicate records.
- Fixed Follow Up Boss people sync pagination to use
idGreaterThan, which prevents later records from being skipped in larger datasets. - Fixed Sierra Interactive lead and task schema handling so optional lead fields and missing
byUserIdvalues no longer break syncs.
Action required
- No action required for existing integrations.
Release window: February 26 - March 4, 2026
New
- Added Follow Up Boss users sync support.
- Expanded Lofty and Cloze communication consent handling defaults.
- Merged connector updates for Outlook and Gmail auth compatibility.
Improved
- Improved credential refresh behavior by normalizing accessors and reset handling after successful refresh.
- Improved inbound webhook handling for soft-deleted credentials.
- Improved Sierra Interactive sync stability under high-volume conditions.
Fixed
- Fixed HighLevel contact schema handling for null and optional fields.
- Fixed Skyslope authentication reliability issues.
- Fixed Gmail scope handling for current auth flows.
Action required
- No action required for existing integrations.
Release window: February 12 - February 25, 2026
New
- Added dashboard callback URL settings for credential sync completion events, including initial-sync-complete notifications.
- Added
@rollout/link-reactsupport forAddCredentialFormanduseCredentials(). - Added credential invalidation support and improved webhook processing reliability.
- Added event
PropertyV2payload support andescrowClosingDatetransaction support.
Improved
- Improved Sierra Interactive call sync coverage by unifying internal and public call data.
- Improved Follow Up Boss coverage with notes ingestion, schema alignment, and tenant whitelabel support.
- Improved migration and deployment reliability.
Fixed
- Fixed Lofty lead and appointment parity issues, including duplicate handling and event type compatibility.
- Fixed Follow Up Boss schema compatibility for events and text messages.
- Standardized database column naming for consistency.
Action required
- If you use Rollout UI components, upgrade
@rollout/link-reactand ensure peer dependencies are installed (@mantine/*,@tanstack/react-query,react,react-dom). - If you want sync-complete notifications, configure callback URLs in Dashboard Settings.
Release window: January 29 - February 11, 2026
New
- Added Microsoft Outlook email sync and deletion sync support.
- Added outbound DB sync coverage for events, appointments, documents, and notes entities.
- Added external DB sync completion callback support for credentials.
- Added Cloze custom-field sync support.
Improved
- Improved Sierra Interactive performance for large syncs with better batching and fetch behavior.
- Improved credential refresh locking and error handling to reduce duplicate refresh paths.
- Improved transform and stale-record processing stability for large datasets.
Fixed
- Fixed Cloze communication consent sync behavior.
- Fixed Skyslope session-refresh error handling and timeout paths.
- Fixed Dotloop batch credential refresh handling to reduce expired-token failures.
Action required
- No action required for existing integrations.
Release window: January 15 - January 28, 2026
New
- Added Google Calendar connector support with calendar and event sync filtering.
- Added Sierra Interactive calls and call-recording sync support.
- Added Dotloop users and transaction participant sync coverage.
Improved
- Improved Skyslope transaction participant coverage, including agent and commission participant updates.
- Improved Sierra Interactive auth UX with API key guidance in the auth component.
- Expanded Sure Send event coverage.
Fixed
- Fixed Skyslope address, user-mapping, and 2FA-related sync reliability issues.
- Fixed Sierra call record URL handling for records with missing/optional fields.
- Fixed Brivity date transform failures.
Action required
- No action required for existing integrations.
Release window: January 1 - January 14, 2026
New
- Added Dotloop people-participant coverage in transaction sync payloads.
- Added Lofty stages entity support.
- Added Gmail inbound webhook flow support.
Improved
- Improved transaction participant modeling with role support.
- Improved Dotloop and credential queue stability for high-volume sync scenarios.
- Improved browser/session resilience for connector authentication flows.
Fixed
- Fixed Dotloop date parsing and account-key handling issues.
- Fixed Skyslope address parsing and user-filtering edge cases.
- Fixed BoldTrail and HubSpot email-message normalization and schema handling issues.
Action required
- No action required for existing integrations.