Set a primary color for action buttons, hover effects, and other elements in the widget. Because the background and button text will be white, this color should be dark enough to provide accessible contrast.
Specify a font-family to use across the widget. You should start with the font-family you want and end with a generic family for the browser to fall back on.
There are two ways to enable additional tabs and configurations in the widget. Some settings, like custom mapping and filters are designed to be dynamically configured in your embed code.Other options, like the ability to run jobs, are configured globally for your environment. By default, your users will only be able to unlink and re-configure credentials via the widget.
Note that this will clone all historical data again. This can create duplicates in your target if you don’t properly handle duplicated data in the script or target.
This will allow users to modify the schedule on which their data is synced.For Widget v3 (Beta), this permission must be on for end users to see and use the Scheduled data syncs screen inside the embedded widget. See the Sync Schedule reference for how that UI behaves once enabled.
When this permission is enabled for your environment, Widget shows a Schedule type field on the Scheduled data syncs screen so users can choose interval (repeat every N minutes or hours) in addition to fixed (calendar-style) schedules.
With this option off (the default), sync timing is configured once per flow.With it on, each linked connector may have its own schedule (connector_id). In the embedded widget, edits made from Scheduled data syncs while a connector is in context are written to that connector’s schedule, not only the flow-level schedule. For how this surfaces in callbacks, see setListeners and Sync Schedule.
