Data Sync

Articles
Excerpt is generated from the doc content.

Introduction

Byteline allows users to synchronize data of two different databases or CMS systems with ease. Whether you want to keep the data of two CMS systems synchronized or want to ensure your databases are synchronized, the platform lets you do it effortlessly.

How to Sync Data between two applications

In this guide, we have uncovered a few simple steps to help you synchronize data between two applications, namely Airtable and Webflow, using Byteline. These instructions are applicable for any two CMS systems or databases.

We have divided this article into four sections to make it easy for you to understand the process of data synchronization on Byteline, as illustrated below:

  1. Configuring Data Sync
  2. Handling Existing Data
  3. Preview
  4. Start Sync
  5. View Records Sync History

Let’s begin.

Configuring Data Sync

In this section, you will learn how to configure two applications, Airtable and Webflow, for data synchronization between them with Byteline.

Select Apps

To configure data synchronization, you first need to select two different applications, which can be done by following the steps mentioned below.

On the New Sync page, click on the Add New button next to the My Syncs in the sidebar menu.

Step 1: Select both apps by either typing the app's name in each text box or scrolling through the list of categorized apps. Once both apps have been selected click "Set up sync". In this example we will be connecting Airtable data with Webflow.

Step 2: Select from a prebuilt template to save time or create your own configuration for complete customization. Each app combination is unique and we have created templates that address specific use cases.

Step 3 (TEMPLATE): Sign in to the apps by clicking the 'Connect [app]' button. Once connected, click 'Next'.

Ensure that pop-ups are disabled, as the new connection dialogs appear in pop-up windows.

Step 4 (TEMPLATE): Grant access to Byteline with the necessary permissioning to keep your sync running.

Step 5 (TEMPLATE): Once you have signed into Airtable, select the desired base from the Airtable base dropdown list. Click 'Next'.

Step 6 (TEMPLATE): Byteline will automatically map fields for you with templates. You can see exactly how the fields are matched by clicking 'review mappings' or click 'Continue for the next step.

Step 7: Once you have signed into Webflow, select the "object type" along with the Site from the dropdowns.

Step 8: Click on the Save & Proceed button.

Select Table(s)

Step 1: Once you select the Airtable base and Webflow site, you can view available tables for both. Choose the desired table from Airtable and Webflow dropdown list. Byteline performs mapping automatically based on the table names.

Note: Users can manually add a table mapping. All they need to do is click the Add another Table button and choose the desired tables from the drop-down list. Multiple tables can be mapped on this screen.

Step 2: After selecting the desired table(s) from Airtable and Webflow, delete all other tables displayed on the screen by clicking on the Trash Bin button.

Note: Users can synchronize the data either two-way or one-way. By default, the sync is set to two-way. You can set the sync one way, either left to right or right to left.

  • Two-way sync: In this type of sync, the data is synchronized bidirectionally whether you create, update, or delete in the Airtable or Webflow.
  • One-way sync: In this type of sync, the data is synchronized only in one direction, right-to-left or left-to-right.

Step 3:  Click on the Save & Proceed button.

Filters

In the table mapping screen, you can configure filter(s) on one or both sides of the sync. The filter only affects the data consumed from the side of the sync where it's configured. For example, if you add a filter on Airtable (above sync) to filter out the records with the empty "Name" field, then it will only sync the Airtable records with some value in the "name" field. It will not have any effect on the records read or created/updated on the Webflow.

Below is a sample filter on the Airtable "Name" field.

Date & Time Filters

Byteline offers robust filtering options, including support for date and time-based filters. These filters can handle both absolute date-times, such as 2020-10-26T16:56, and relative formats like -30d (for the past 30 days). For a detailed guide on using date and time formats in filters, visit our documentation on writing dates.

Selecting Data To Sync

When setting up your sync, you can choose from three options to determine which data should be synchronized.

Both Existing and Future Data

This option ensures that all your data—both past and future—remains in sync. It works in two stages:

  • Historical Sync: All existing data is synced.
  • Ongoing Sync: Once the sync is live, it continuously updates with new changes.

Choose this option if you want a fully synchronized dataset that includes historical data and stays up to date with future changes.

Existing Data Only

This option syncs only the existing data at the time of execution. It does not keep syncing new changes after the initial run.

  • Ideal for one-time syncs.
  • You can manually rerun the sync whenever needed.

Use this if you only need a snapshot of your current data without keeping the sync always running.

Future Data Only

This option starts syncing only new data changes from the moment the sync goes live. Any existing data before the sync starts is ignored.

Note: Since past data is not synced, only records that change after the sync starts will be in sync. Older records may remain out of sync.

Choose this option if you only need to track new and updated records going forward.

Configure Field Mapping

Field mapping tells Byteline which fields to connect between your apps. For example, map Email in one app to Email Address in the other.

Byteline suggests mappings automatically. Review them before continuing:

  1. Click Show field matching to expand the mappings.
  2. Check each field pair and change any incorrect matches.
  3. Use Add mapping to include additional fields, and remove mappings you do not need.
  4. Make sure all fields marked Required are mapped.
  5. Review each field's sync direction, where available. Field-level direction controls future changes; the initial sync of existing records uses the direction selected for the table or collection.

During the initial sync, mapped destination fields may be overwritten with source values. If your setup includes existing data, review the sync preview before starting.

When your mappings are ready, click Continue.

For detailed instructions on field directions, read-only fields, fixed values, select options, and empty values, see Field Mapping.

Existing Data

Byteline allows you to sync your existing data for the tables configured for the sync. Simply choose the direction in which the data should be synced by selecting one of the arrow buttons on the screen below.

Once the direction is selected, click the "Save & Proceed" button to continue.

For details on the syncing existing data, check out our Historical Sync documentation.

Preview (for existing data)

On the next screen, you'll see a preview with a summary of the records that will be impacted for each table. This includes the number of records that will be created, updated, and deleted for the selected CMS systems.

Note: The sync hasn't started yet. This is just a preview of what will occur once the sync begins.

Records to be deleted

When syncing existing data, some records may be marked for deletion. Byteline gives you the ability to review these records in advance, providing peace of mind by ensuring that only expected records are deleted.

To view the details of these records, click the red-underlined link for each "Will delete items" value. This will open a pop-up displaying the records to be deleted in a table format.

You can also export these records as a CSV file for backup purposes.

When no existing records can be matched

Sometimes Byteline cannot confidently match records that already exist in both apps. For example, you may have 200 contacts in one app and 10 customers in another app, but none of them share the same matching values.

When this happens, Byteline will ask you how you want to continue:

Add records as new Choose this if you want to keep the existing records in the destination app. Byteline will create the source records as new records. This is the fastest option, but it may create duplicates if some records already exist in the destination app.

Clear the destination app first Choose this if you want a clean import with no duplicates. Remove the existing records directly in the destination app, then return to Byteline and check again.

Byteline does not remove existing destination records for you during this step. Existing records stay unchanged unless you remove them in the destination app.

Start Sync

After you're satisfied with the Preview results, click on the Start Sync button.

Once the synchronization is complete, a message will appear on the screen saying, Historical data sync completed successfully! and Sync successfully turned live! Changes will actively sync. After a few seconds, you will be automatically redirected to the Change History page.

View Records Sync History

Byteline allows the users to view the record-level history of all the data synchronization made between CMS systems with ease.

On the Change History page, you can view the history of any of the changes made in both Airtable or Webflow. For example, if you make any change in one of the CMS systems, it will be automatically reflected on the other system that you have connected for data synchronization.

In this case, whether you make any changes in Airtable or Webflow, it automatically changes in the other one. You do not need to make changes in both tables manually.

Field Mapping Rules

Handling multiple values mapped to a single field

If a source field (such as phone numbers or emails) contains multiple values, and you map it to a single-value field on the destination, Byteline will sync only one value.

– When the source has a “primary” value (e.g., primary phone), the primary is used.

– If no primary is defined, the first value in the list is used.

This ensures predictable results for your syncs.

How empty field values are handled

Byteline handles empty field values differently when creating a new record versus updating an existing record.

When Byteline creates a new record in the destination app, empty source fields are skipped by default. This means Byteline does not send empty values just to clear or overwrite fields in the destination app.

This helps protect default values, required setup, or app-specific behavior in the destination app.

For example, if a source record has a name but its description is empty, Byteline will create the destination record with the name and leave the description field untouched.

Source record:
Name: Blue Shirt
Description: empty

Destination record created:
Name: Blue Shirt
Description: left unchanged or handled by the destination app

After a record has already been created or matched, mapped fields stay in sync. If a user later clears a mapped field in the source app, Byteline will also clear the corresponding field in the destination app.

For example:

Before update:
Source Description: Lightweight cotton shirt
Destination Description: Lightweight cotton shirt

User clears Description in the source app.

After sync:
Source Description: empty
Destination Description: empty

This behavior keeps synced records accurate while avoiding unwanted overwrites during record creation.

Important: Byteline only clears a destination field when the source field is clearly emptied. If a field is missing from an app response, unavailable, or not included in the sync, Byteline does not treat that as a cleared value.

Understanding Sync Issues

When Byteline syncs your data between two apps, it occasionally runs into something it can't complete on its own — for example, a required field is empty, an app rejects a value, or a connection needs to be reauthorized. Instead of burying you in hundreds of individual record errors, Byteline groups these into a small number of clear, actionable Sync Issues.

Think of a Sync Issue as a single, plain-English summary of one problem, along with the list of records it's affecting and, where possible, a one-click button to fix it.

How sync issues are created

As your sync runs, any record that can't be synced generates an error or a warning. Rather than showing each one separately, Byteline rolls related errors up into a single issue so it's easy to understand and fix.

The grouping is smart — errors are combined by what actually caused them, for example:

  • One issue per problem type — e.g. "A connection has expired" appears once, not once per record.
  • One issue per field — e.g. all records failing because of the same field mapping are grouped together.
  • One issue per specific value — e.g. if a dropdown option is missing in your target app, each missing option becomes its own issue (so "Add the 'Marketing' option" is separate from "Add the 'Sales' option").
  • One issue per record — for problems that are genuinely specific to a single record.

Each issue shows:

  • A short description of what went wrong and how to fix it.
  • Whether it's an Error (sync is blocked for those records) or a Warning (records synced, but something needs your attention).
  • The number of affected records, and the list of those records.

As the same problem recurs, Byteline keeps adding the newly affected records to the same issue and updates the count — so the issue list stays short and meaningful.

Sync issues can resolve themselves automatically

Most issues need you to take action to fix them — but some clear on their own once the underlying cause is resolved, so you won't have to chase down every record manually. Here's when an issue resolves automatically:

  • When affected records sync successfully. Byteline watches your ongoing syncs. As each affected record syncs cleanly, it's removed from the issue. Once every affected record has synced successfully, the issue is automatically marked as Resolved.
  • When you reconnect an app. Issues caused by an expired connection or missing permissions resolve automatically after you reconnect the affected app.
  • When you upgrade your plan. Issues caused by reaching a plan's sync limit resolve automatically once you're on a higher plan.
Good to know: An affected record is cleared only when that specific record syncs again cleanly. If a record that previously failed doesn't change again, it won't re-sync on its own — so an issue can keep showing older affected records until those records are re-synced or you resolve the issue manually. If you've fixed the root cause and just want the issue gone, you can mark it as Resolved yourself.

One-click fixes

Wherever Byteline can fix a problem for you, the issue includes an action button so you don't have to leave the app or edit anything by hand.

A common example is a missing dropdown/select option in your target app. When a value coming from the source app doesn't exist as an option in the target field, you'll see a button like:

Add 'Marketing' option and retry 12 records

Clicking it does both steps for you:

  1. Adds the missing option (in this example, "Marketing") to the field in your target app.
  2. Retries the affected records so they sync with the newly added option.

Other issues offer similar helpers depending on the problem — for example, reconnecting an app, adjusting a field mapping, or marking an issue as resolved once you've fixed it elsewhere. You'll only see the buttons that make sense for that particular issue.

Email notifications

Byteline emails you about open issues so you don't have to keep checking the dashboard — but it batches them so you're never spammed:

  • Errors: at most one email every 12 hours. (When a fresh batch of errors starts, Byteline waits a short time to collect related errors before sending, so you get one useful summary rather than a flood.)
  • Warnings: at most one email every 24 hours, since warnings are less urgent.

Each email summarizes the pending issues for your sync, so you can jump straight in and resolve them.

Updated
November 13, 2026
Excerpt is generated from the doc content.

Field mapping tells Byteline which fields contain corresponding information in your connected apps. For example, you can map Email in one app to Email Address in the other, even though their names differ.

For each mapping, you choose which fields to connect and, where supported, which direction future changes should travel.

Review and edit your field mappings

After selecting the tables or collections to sync, review their field mappings.

  1. Click Show field matching if the mappings are collapsed.
  2. Review the automatically suggested mappings. Check that each pair contains the information you want to sync.
  3. To change a mapping, use the field dropdown to select a different field.
  4. Click Add mapping to include another pair of fields.
  5. Remove any mappings you do not need.
  6. Review the sync direction for each mapping, where available.
  7. Make sure all fields marked Required are mapped before continuing.

For example:

Field in the left appField in the right appInformation synced
Full NameNameThe person's name
EmailEmail AddressThe person's email address
CompanyCompany NameThe person's company

Choose fields that represent the same information and can accept the values being sent. Similar field names do not always mean the fields belong together.

When syncing existing records, mapped destination fields may be overwritten with source values. Review your mappings and the initial sync preview before starting.

Choose the field-level sync direction

Field-level direction controls how future changes move between mapped fields during ongoing sync. Use the direction control on the mapping to select an available direction.

DirectionWhat happens during ongoing sync
Left → RightChanges to the left field are sent to the right field. Changes to the right field are not sent back.
Left ← RightChanges to the right field are sent to the left field. Changes to the left field are not sent back.
Left ↔ RightChanges to either field can update the corresponding field in the other app.

For example, in a two-way sync, you might keep contact details synchronized in both directions while allowing a reporting field to receive updates from only one app.

The available directions depend on the connected apps, fields, and sync configuration.

Initial sync versus ongoing sync

The initial sync of existing records runs in one direction, selected for the table or collection. Field-level directions configure ongoing updates; choosing a two-way field mapping does not make the initial sync two-way.

Check both the initial sync direction and the field-level directions before starting.

Required and read-only fields

Required fields

Fields marked Required must be mapped. Make sure the source provides valid values for these fields. A mapping alone does not prevent an error if a required value is empty or rejected by the destination app.

If every record should receive the same value, you can use a fixed value instead of a source field.

Read-only fields

Read-only fields, such as record IDs and calculated fields, can supply values but cannot receive updates from the other app.

For example:

Notion ID → Airtable “Notion ID”

Byteline can copy the Notion record ID into a writable Airtable field. Editing that Airtable field does not change the original Notion ID.

When a read-only field is mapped, its direction is restricted so that it acts as the source.

Use a fixed value

Use a fixed value when a destination field should receive the same value for every synced record. For example, set a Source field to Byteline.

  1. Open the field dropdown for the field you want to set.
  2. Select Use fixed value at the bottom of the dropdown.
  3. Enter or select the value.
  4. Save the mapping.

The input depends on the destination field type: text fields accept text, number fields accept numbers, boolean fields accept true or false, and select fields let you choose an allowed option.

Fixed values are one-way. There is no source field in the other app to receive changes back.

Map one field to multiple fields

You can send one source field to more than one field in the connected app.

For example, you might use the same source Email field to populate both Contact Email and Notification Email in the destination.

These mappings follow three rules:

  • Only one mapping from that field can be two-way.
  • Additional mappings from the same field must be one-way.
  • Each receiving field can have only one source field.

For example:

MappingDirection
Email ↔ Contact EmailTwo-way
Email → Notification EmailOne-way

Map select and multi-select options

Select fields may use different labels for the same choice. For example, one app might use Active, while the other uses Open.

To pair different labels:

  1. Click Map options on the select or multi-select field mapping.
  2. Pair the corresponding options, such as Active and Open.
  3. Add more pairs as needed.
  4. Click Apply mapping.

Options with matching names do not need an explicit pair.

By default, Byteline automatically creates missing options when the destination app supports it. You can turn off Automatically create missing options under Map options if the destination's option list should stay fixed.

If a missing option cannot be created, its value is skipped and a sync issue is raised. For multi-select fields, each value is handled separately. Previewing a sync does not create options; they are created when the sync writes data.

See Automatically creating select options for details.

Map multiple values to a single-value field

Some source fields contain several values, such as multiple phone numbers or email addresses. If you map one of these to a destination field that accepts only one value, Byteline sends:

  • The primary value, if the source identifies one.
  • Otherwise, the first value in the list.

For example, a contact's primary phone number is used when syncing several source phone numbers into one destination phone field.

Understand empty field values

Byteline treats empty values differently when creating a record and when updating a record that has already been created or matched.

SituationBehavior
Creating a record with an empty source fieldByteline skips that empty field by default, allowing the destination app to handle defaults or other field behavior.
A user clears a mapped source field on an already-created or matched recordByteline also clears the corresponding destination field, following the mapping's sync direction.
A field is missing from an app response, unavailable, or not included in the syncByteline does not interpret this as the user clearing the field.

For example, if a synced description contains Lightweight cotton shirt and you later clear the source description, Byteline clears the corresponding destination description too.

Map fields in different languages

If your app stores languages in separate fields, map each one to its corresponding destination field. For example, map Title_EN to the English title field and Title_FR to the French title field.

See Multilingual Content Support for details, including considerations for apps with native localization features.

Change mappings on a live sync

Open the sync from My Syncs, click Edit, and update the field mappings. The running sync continues using its current settings while you edit.

Review the save screen to see how your changes will apply. Saving a mapping change for future activity does not automatically update already-synced records. Where available, choose Update already-synced records to apply the changed mappings to records the sync has already connected.

Some changes require a restart. Follow the action shown on the save screen.

See Editing a Live Sync for the full workflow and available save options.

Updated
November 13, 2026
Excerpt is generated from the doc content.

Introduction

When you map a single-select or multi-select field, Byteline matches values by option name. Options with the same name sync on their own. If the source has a value the target field does not have, Byteline can add that option to the target field and then write the value.

This is on by default for mappings whose target app can add select options. You can turn it off from Map options on the field mapping.

How it works

  1. Byteline looks up the source value against the target field’s options (by name, or by a pair you set under Map options).
  2. If there is no matching option and auto-creation is on, Byteline adds the option to the target field and writes the record.
  3. If auto-creation is off — or the target app cannot add options — the value is skipped and a sync issue is raised. From that issue you can add the option yourself and retry the affected records, or map the value to an option that already exists.

For a multi-select field, each value is handled on its own. Values that already have an option are written; only the missing ones are created (or reported).

A sync preview does not add options. Options are added only when the sync actually writes.

Mapping options with different names

Use Map options when the two sides use different labels for the same choice — for example, Active → Open.

  1. Open the sync and go to field mapping.
  2. On a select or multi-select mapping, click Map options.
  3. Pair a left option with a right option. Add more rows as needed.
  4. Click Apply mapping.

Options with matching names do not need a row. Add a mapping only when the names differ.

Turning auto-creation off

Use this when you do not want Byteline to add options to the target app — for example, a Status field whose list should stay fixed.

  1. Open Map options on the field mapping.
  2. Turn off Automatically create missing options.
  3. Click Apply mapping.

The mapping link then reads Options not auto-created. Missing values raise a sync issue instead of adding an option.

Turn the toggle back on to restore automatic creation. The toggle appears only when at least one write-target app for that mapping can add select options.

When a sync issue is still created

A sync issue is created when:

  • Automatically create missing options is off for that mapping.
  • The target app cannot add options (the toggle is hidden).
  • Byteline could not add the option (for example, the app rejected the create).

From the issue you can add the option and retry, map the value to an existing option, or ignore the records

Updated
November 13, 2026
Excerpt is generated from the doc content.

Introduction

Once a sync is live, you can change its configuration without stopping it first. Byteline keeps the sync running on its current settings while you edit, then shows you exactly what saving will do before anything changes.

Use this when you need to:

  • Add, remove, or change field mappings
  • Adjust sync direction on specific fields
  • Update filters, matching keys, or table setup
  • Fix a mapping after records fail to sync

For first-time setup, see Data Sync - Getting Started. For how ongoing updates work after go-live, see Ongoing Sync (Real-Time & Scheduled Updates).

How to edit a live sync

  1. Open My Syncs in the Byteline console.
  2. Click the sync you want to change.
  3. Click Edit.

If the sync is running, Byteline creates a draft of your configuration. The live sync continues using its current settings until you save.

While you edit, a banner at the top confirms:

Editing a live sync
This sync will continue running while you make changes. Saved changes will apply after you save.

What happens while you edit

  • The sync keeps running on its existing configuration.
  • New changes in your apps keep syncing according to the current (not yet saved) setup.
  • Your edits are stored as a draft until you save or discard them.
  • If you leave editing without saving, you'll see a reminder that you have unsaved changes. The sync still runs on its current settings until you save.

You can click Resume editing to return to your draft and finish.

Saving your changes

When you finish editing a live sync, Byteline shows a save review screen instead of a preview run. A preview is useful when setting up a sync for the first time; for a live sync, what matters is how your changes will be applied.

Byteline analyzes your changes and tells you:

  • Whether the sync can keep running after save
  • Which table pairs are affected
  • Whether existing records need to be re-checked or re-imported

Then you choose how to save.

Your save options

Depending on what you changed, you'll see one of the following.

1. Save changes (applies to future sync activity)

When: Your change is a field mapping update that does not require restarting the sync.

What it does:

  • Saves your changes immediately.
  • The sync keeps running without stopping.
  • Future creates, updates, and deletes use the new mapping.
  • Already-synced records are not changed.

This is the recommended option for most field mapping tweaks when you only care about new activity going forward.

2. Update already-synced records

When: You changed field mappings on a sync that keeps matched records (not “Future data only” or “Historical only”).

What it does:

  • Saves your field mapping changes.
  • Re-applies the changed mappings to records this sync has already connected.
  • The sync does not stop or restart.
  • Matching, creating, and deleting records are not re-run — only the mapped fields you changed are updated.

Use this when you fixed a mapping and want that fix reflected on data that's already synced.

3. Stop and restart sync

When: Your change affects the sync setup in a way that requires listeners or existing data to be rebuilt.

What it does:

  • Saves your changes.
  • Stops and restarts the sync to apply them.
  • Rebuilds what the sync listens to and, where needed, re-checks existing records.

You'll see this when changes affect things like:

  • Table mappings (adding or removing tables)
  • Matching keys (when manually configured)
  • Record filters
  • Sync mode (e.g. existing + future data vs future only)
  • Field mapping changes that change the overall sync direction for a table (e.g. one-way → two-way)

The save review lists Tables affected and marks each as Restart needed or Re-import needed. Unaffected tables keep syncing until the restart completes.

What kind of change needs what?

ChangeTypical result
Edit field mapping (same direction)Save without stopping; optional update of already-synced records
Add or remove a field mappingSave without stopping; optional update of already-synced records
Change option/value mapping on a fieldSave without stopping; optional update of already-synced records
Change sync direction on fields (e.g. one-way → two-way at table level)Stop and restart sync
Change matching keys (manual)Stop and restart sync; may re-import existing data
Change record filtersStop and restart sync; may re-import existing data
Add or remove a table pairStop and restart sync
Change sync modeStop and restart sync
Change app object type (e.g. different Webflow collection type)Stop and restart sync

If you're unsure, complete your edits and review the save screen — Byteline tells you the required action before you commit.

After you save

Changes applied without restart

You'll see a confirmation such as:

Changes saved. Your sync picked them up without stopping.

If you chose Update already-synced records, you'll also see progress while existing records are updated. The sync stays live throughout.

Changes that need a restart

If your change requires a restart, the sync keeps running on the old configuration until you stop and start it. You'll see:

Your changes are saved and take effect on the next start. The sync keeps running on its current settings until then. Please stop and start the sync to apply them.

Click Stop & Restart Sync to apply the saved changes.

If the sync is already stopped when you save, you'll see:

Your changes are saved and take effect when you start this sync.

Start the sync when you're ready.

Discarding changes

On the save review screen, click Discard changes to throw away your draft and return to the live configuration. The running sync is unaffected.

Editing a stopped sync

If the sync is not live, Edit opens the same wizard, but there is no “editing live” banner and you'll get a normal preview on the last step (when applicable) rather than save review.

Common scenarios

Fix a field mapping after sync errors

  1. Open the sync and click Edit, or click Edit Field Mapping from the error banner.
  2. Update the mapping on the Choose & match your data step.
  3. On save review, choose:
    • Save changes — fix applies to new activity only, or
    • Update already-synced records — fix also updates records already connected by this sync.

Add a new mapped field to a live sync

  1. Edit the sync and add the field mapping.
  2. Save changes to apply it to future sync activity.
  3. Optionally choose Update already-synced records to populate the new field on existing matched records.

Change which records are included (filters)

  1. Edit the sync and update the filter.
  2. Save review will require Stop and restart sync because records excluded by the old filter were never synced and need to be re-evaluated.
  3. Stop and restart to apply.

Related documentation

Updated
November 13, 2026
Excerpt is generated from the doc content.

Ongoing Sync keeps your connected apps continuously up to date after the sync goes live. Once enabled, Byteline listens for changes in your source app and automatically applies those changes to the destination app based on your configured sync direction and field mappings.

Byteline supports ongoing sync through both real-time webhooks and scheduled polling. Depending on the app, changes may sync instantly or within up to 15 minutes. The exact timing depends on how the source app exposes changes.

Ongoing sync applies only to new, updated, or deleted records going forward. It does not reconcile existing data or re-evaluate matching keys—that process is handled separately by Historical Sync. Once ongoing sync is active, Byteline tracks changes using the established record links created during setup or historical sync.

How Changes Are Detected

Byteline detects changes in connected apps using one of two methods: webhooks or scheduled polling. The method used depends on what the source app supports and requires no configuration from you.

For apps that support webhooks, changes are sent to Byteline as soon as they happen. This allows updates—such as new records or field changes—to sync in near real time, often within seconds.

For apps that do not support webhooks, Byteline uses scheduled polling to check for changes at regular intervals. In these cases, updates may take up to 15 minutes to sync. Polling runs automatically in the background and ensures changes are eventually captured even when instant notifications are not available.

Regardless of the detection method, all changes go through the same validation, mapping, and delivery process before being applied to the destination app.

What Changes Are Synced

During ongoing sync, Byteline monitors the source app for record changes and syncs them to the destination app based on your configured sync direction and field mappings.

The following types of changes are synced:

Record creation

When a new record is created in the source app, Byteline creates a corresponding record in the destination app and populates it using your configured field mappings.

Record updates

When an existing record is updated in the source app, Byteline syncs the changes to the corresponding record in the destination app. Only mapped fields and fields with an active sync direction are updated.

Record deletion

When a record is deleted in the source app, the corresponding record is also deleted in the destination app. This ensures both apps remain consistent and prevents orphaned or outdated records from persisting in the destination.

All changes are applied using the existing record linkage established during setup or historical sync. Byteline does not attempt to re-match records during ongoing sync.

Sync Direction in Ongoing Sync

In ongoing sync, Byteline does not use a single one-way or two-way setting at the sync level. Instead, sync direction is defined at the field level, and ongoing sync behavior is computed based on those field-level rules.

For each mapped field, you choose the direction in which changes are allowed to flow between apps. When a record changes, Byteline evaluates the modified fields and syncs only the changes that match the configured direction for each field.

Fields not included in the field mapping are ignored during ongoing sync. Changes to unmapped fields do not trigger updates and are not synced to the other app.

This field-level approach allows different apps to remain the system of record for different parts of the same record, while preventing unintended updates to fields you have not explicitly mapped.

Field-Level Direction and Exclusions

Ongoing sync in Byteline operates strictly based on field mappings. Only fields that are explicitly mapped between the source and destination apps are considered during sync.

For each mapped field, the configured direction determines whether a change is eligible to be synced. If a change occurs in a field that does not allow syncing in that direction, the change is detected but intentionally ignored.

Fields that are not included in the field mapping are excluded entirely from ongoing sync. Changes to these fields do not trigger updates and are never applied to the other app.

Some fields in destination apps are read-only or system-managed, meaning they cannot be written to through the destination app’s API. For such fields, Byteline only allows the field to be mapped in the direction from the read-only app to the other app. Changes to read-only fields are still detected in the source app, and they can be synced outward to the other app—but Byteline will not attempt to write to that read-only field.

This field-level control ensures that only the intended data flows between apps, prevents accidental overwrites, and allows each app to remain authoritative for specific fields.

What Happens When a Change Fails

If a change cannot be synced during ongoing sync, Byteline records the failure and surfaces a detailed error message explaining why the change was not applied. Common reasons include API validation errors, permission issues, rate limits, or destination app constraints.

Failed changes do not stop the overall sync. Byteline continues processing subsequent changes while tracking failures independently.

All failed changes are visible in the sync activity or change history, where you can review the exact error returned by the destination app. Once the underlying issue is resolved, you can resync failed records to retry syncing those changes without rerunning historical sync or affecting successfully synced records.

Resyncing reprocesses only the failed changes using the latest field mappings and sync rules, ensuring a safe and targeted recovery.

Resyncing Failed Records

When a change fails during ongoing sync, Byteline marks the affected record as failed and provides a detailed error explaining what went wrong. You can review the failure reason, resolution tips, and technical details directly from the failed record view.

Once the underlying issue is resolved—such as fixing validation errors, adjusting inventory, updating permissions, or correcting field values—you can use the Resync button to retry syncing the record.

Clicking Resync re-attempts syncing the record using the most recent data and the current field mappings and sync rules. Only the failed record is retried; other records are not affected.

Resyncing does not rerun historical sync and does not re-evaluate matching keys. It is a targeted recovery mechanism designed to safely retry a single failed change without disrupting the rest of the ongoing sync.

Best Practices for Ongoing Sync

Before enabling ongoing sync, ensure your field mappings and sync directions are configured correctly. Since ongoing sync relies on these rules to determine how changes flow between apps, careful setup helps prevent unintended updates later.

If you make schema changes, update permissions, or modify field mappings, it’s recommended to review recent sync activity and address any failed records promptly. Use the Resync option to retry failed records once issues are resolved, rather than rerunning historical sync.

Remember that ongoing sync applies only to future changes. If you need to reconcile existing data or establish record relationships, use Historical Sync before relying on ongoing sync.

By combining historical sync for initial alignment and ongoing sync for continuous updates, Byteline ensures your connected apps remain consistent, reliable, and up to date over time.

Updated
November 13, 2026
Excerpt is generated from the doc content.

When you create a new Sync in Byteline, the first step is to choose the two apps you want to connect. Based on the selected apps, Byteline automatically shows you a set of pre-built Sync templates that are designed to get you up and running quickly. If no template is available for the selected app pair, Byteline will take you directly into the Sync configuration so you can build it from scratch.

Sync templates save time by providing a fully pre-configured setup specific to the apps you are integrating. Instead of manually configuring every mapping, field, and workflow step, templates let you start with a complete blueprint—so you only provide the few details that are unique to your environment.

How Templates Work

Once you select your two apps, Byteline displays the templates available for that particular app combination. For example, when you select Webflow and Printful, you’ll see the following templates:

  1. Sync Products (Printful → Webflow)This template automatically syncs your Printful products into Webflow eCommerce, including product details, variants, pricing, and images.Only minimal inputs are required—for example, selecting your Webflow eCommerce site. All other configurations, mappings, and workflows are pre-built for you.
  2. Sync Orders (Webflow → Printful)This template sends new Webflow eCommerce orders directly to Printful for fulfillment.The workflow is already configured to handle order data, customer information, and line items. You only provide the connection details for your Webflow site and Printful account.
  3. Start From ScratchIf you prefer full control, you can build a Sync without using any template. This option starts with a blank configuration where you manually set up each part of the sync—connections, mappings, filters, field transformations, and more.This is ideal for advanced users or custom workflows that do not match the pre-built templates.

Why Use Templates?

Templates save you significant setup time by providing a ready-made configuration tailored to the selected apps. Each template includes:

  • Pre-configured table mapping so you don’t have to determine how objects relate across the two apps.
  • Pre-mapped fields that automatically connect source fields to destination fields—no manual matching required.
  • Pre-configured unique keys to correctly identify and match records between the two systems.
  • Best-practice defaults created by Byteline experts to ensure reliable and optimized syncing.
  • Minimal required inputs, such as selecting your Webflow site or Printful store.

With templates, you skip the detailed configuration work. Just provide the few inputs specific to your setup, and Byteline handles everything else.

When To Use "Start From Scratch"

Choose this option if:

  • You need a fully custom sync not covered by existing templates
  • Your workflow has unique logic or conditions
  • You want total control over mappings and filters.

This option gives you the highest flexibility but requires more setup effort.

Updated
November 13, 2026
Excerpt is generated from the doc content.

Introduction

Byteline Data Sync efficiently synchronizes existing data in both apps so that you can keep valuable data. This process is called historical sync. The process involves getting existing data from both apps and then updating, creating and deleting records to make the data in sync.

For 2-Way sync, records can be updated on both apps. However, for 1-Way sync, records are updated only on the target app.

Understanding Matching Keys in Data Sync

When you're syncing data between two different apps using Byteline's Data Sync, you want to make sure that the information is matched up correctly. This is where matching keys come into play. Don't worry if you're not a tech expert—this guide will break it down for you in simple terms.

What Are Matching Keys?

Think of matching keys as special identifiers for your data. Imagine you have two lists—one from App A and one from App B—and each list contains names and email addresses. A matching key could be something like an email address because it’s a piece of information that is unique to each person on your list. No two people should have the same email address, right? So, this unique piece of information helps Byteline figure out who’s who when syncing the data between your two apps.

Matching keys might sound technical, but they’re really just a simple way to make sure your data stays accurate when syncing between apps. By using matching keys, Byteline ensures that your information is always matched up correctly, saving you time and hassle.

Why Are Matching Keys Important?

When you’re syncing data, you might have records in both App A and App B that need to be matched up. If you don’t use matching keys, Byteline won’t know how to correctly pair the records from one app to another. Matching keys ensure that the information for "John Doe" in App A matches up with the information for "John Doe" in App B, even if the two apps store the data slightly differently.

How Do Matching Keys Work?

  1. Matching Key Selection:
    1. Automatic (default): Byteline automatically determines the matching keys based on your data. This default approach works for most of the sync configuration. However, for fine control over the historical sync process, you can manually select the matching keys.
    2. Manual: For greater control over the historical sync process, you can manually select matching keys. The first step in the manual selection is to decide what your matching key will be. In many cases, it’s something straightforward like an email address or a customer ID. You’ll pick this key when setting up your data sync for the first time. See the Manually Configuring Matching Key(s) section below for the details.
  2. Historical Sync: When you run your sync for the first time, Byteline looks at the matching keys you’ve chosen to match up existing records between your two apps. This process is called a historical sync, meaning it’s looking at data that’s already there, not just new data.

    Matching keys are only considered for the historical sync, i.e., to sync existing data. Once a sync is active, matching keys are not checked.

Manually Configuring Matching Key(s)

To manually select matching keys for real-time sync:

  1. During configuring real-time sync, you need to toggle the option to manually choose the unique key(s). Below is the screenshot for enabling this setting.

  2. Click the Continue button, which takes you to the matching key configuration page. On this page, define your matching keys by clicking on the key icons (illustrated in the screenshot)

How to trigger historical sync?

The historical sync is automatically performed when a sync is started. The only exception is if you choose the "Future data only" option, in which case historical sync is skipped. Once a sync is live, our ongoing sync process will keep your data in sync.

If you're planning to change the structure of your tables and want to perform historical sync afterward. You should follow the below steps:

  1. Stop the sync.
  2. Make modifications to your table(s) structure.
  3. Edit the sync for the new table structure.
  4. Make the sync live, which will perform the historical sync.

Ignoring or Deleting Unmatched Records

Historical sync is a one-way process, allowing you to sync data either from left to right or right to left. If the target app contains more records than the source, these extra records are considered unmatched. You can choose to either leave these records unchanged or delete them.

If your sync includes multiple tables, you can configure this setting individually for each table.

Deleting Unmatched Records

If at least one unmatched record is detected, an option to manage these records appears. To delete the unmatched records:

  1. Select the "Delete items" radio button.
  2. Click the "Apply" button.

When the historical sync runs, it will automatically remove the unmatched records from the target app.

Note: You can click on the unmatched record count to view details of the records before making a decision

How Byteline Handles Changes During Historical Sync

Historical sync copies your existing records from one app into the other, in a single direction that you choose. We'll use a common example throughout: a sync that copies records from Airtable into Notion. In this case Airtable is the source (the app being copied from) and Notion is the destination (the app being copied into). The same behavior applies to any pair of apps — for example, HubSpot and Google Sheets.

While this one-time catch-up is running, here's what happens to any new changes people make.

Changes in Airtable (the source) keep syncing

You don't have to stop working. If someone adds or edits a record in Airtable after the historical sync has started, Byteline still picks up that change and syncs it to Notion.

And if you happen to edit the same record that the historical sync is also working through, your most recent change wins. Byteline recognizes that your live edit is newer than the data the historical sync started with, keeps your latest version, and won't create a duplicate.

Changes in Notion (the destination) are paused during historical sync

If you have a two-way sync between Airtable and Notion, changes normally flow in both directions. But while the historical sync from Airtable → Notion is running, Byteline temporarily ignores changes made in Notion (the Notion → Airtable direction is paused).

This is intentional. During the initial catch-up, Byteline is writing a large number of records into Notion. Pausing the Notion → Airtable direction keeps those sync-generated writes from bouncing back and causing conflicts, loops, or duplicate records. Two-way syncing turns back on automatically as soon as the historical sync finishes — you don't need to do anything.

Tip: Because edits made in Notion won't sync back to Airtable until the historical sync completes, it's best to hold off on important changes in Notion (the destination) while the initial sync is running. Make your edits in Airtable, or wait until the sync finishes.

Watch progress and review changes as they happen

You don't need to keep your browser open or wait around — the sync runs on Byteline's servers. While it's working:

  • A progress indicator shows how far along the historical sync is.
  • Your sync history updates live, so you can review each record as it's created or updated, instead of waiting for a summary at the end.

When the sync reaches 100%, the catch-up is complete: real-time syncing (including Notion → Airtable for two-way syncs) is fully active, and your sync history reflects everything that was processed.

What Happens After Historical Sync

Historical sync is designed to reconcile and align existing data between your connected apps. It establishes record relationships, applies matching rules, and ensures both sides start from a consistent state.

If your sync is configured in Existing Data and Future Changes mode, Byteline automatically transitions from historical sync to ongoing sync once the historical sync completes successfully. No additional action is required.

During ongoing sync, Byteline uses the record relationships established during historical sync to keep your apps up to date with new creates, updates, and deletes. Matching keys are not re-evaluated once the sync is live. You can learn more about how ongoing updates work in the Ongoing Sync (Real-Time & Scheduled Updates) documentation.

If your sync is configured in Existing Data Only mode, the sync stops after historical sync completes and no ongoing updates are applied.

Using historical sync for initial alignment and ongoing sync for continuous updates ensures your connected apps remain consistent over time without repeatedly reprocessing existing data.

Troubleshooting

The record count doesn't match

You have completed the historical sync but subsequently discovered a discrepancy in the record counts between the tables of the two apps. This situation often arises when incorrect unique key(s) are selected. Occasionally, a field designated as a unique key may not be truly unique. To ensure accuracy, you can verify the validity of the unique key(s) by counting the distinct values across all rows. The resulting count should match the total number of rows.

Please note that you have the option to select multiple fields as unique. In such cases, Byteline considers the values of both fields as criteria for matching records (using an AND condition).

Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive document will walk you through the step-by-step configuration process for Airtable data sync and address specific use cases tailored to Airtable.

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers usages of data sync features valid for all integrations.

Configuring an Airtable Data Sync

Follow these steps to configure your Airtable sync. After completing the setup, Byteline will generate a preview of the changes that will be made when the sync starts.

Step 1: Start the Sync Setup

  1. Log in to your Byteline account.
  2. Go to the My Syncs page.
  3. Select Create Sync.

Step 2: Choose the apps to connect

Select Airtable as one of the apps in your sync.

You can choose Airtable as either the first or second app, depending on the direction in which you want your data to move.

After selecting both apps, click Set up sync.

Step 3: Start from scratch or use a template

Choose how you want to configure the sync:

  • Start from scratch: Configure each part of the sync yourself.
  • Use a template: Start with a recommended configuration for a common use case.

Templates can make setup faster when one matches your requirements. In this guide, we will select Start from scratch.

Step 4: Select the type of data to sync

Some apps contain multiple types of data, such as contacts, products, orders, or collection items. When prompted, select the type of data you want to sync.

You do not need to select a data type for Airtable. You will choose the Airtable base and tables later during setup.

Step 5: Choose when records should be synced

Select which records Byteline should include:

  • Existing data: Sync records that are already in your apps.
  • Future changes: Sync new records and changes made after the sync starts.
  • Existing data and future changes: Sync the current records first, and then keep future changes synchronized automatically.

A sync preview is generated when your configuration includes existing data. If you select future changes only, you can start the sync without reviewing an initial data preview.

Select whether to sync existing records, future changes, or both.

Step 6: Choose the sync direction

Select the direction in which data should move between the two apps.

Depending on the apps and data types selected, you may be able to choose:

  • One-way sync: Changes move from one app to the other.
  • Two-way sync: Future changes move in both directions.

The initial sync of existing records can only run in one direction. Therefore, when you select a two-way sync, you must also choose which app should be the source for the initial data sync.

For example, you can initially copy existing records from Airtable to Webflow and then keep future changes synchronized in both directions.

Step 7: Connect and set up your apps

Next, connect the accounts that Byteline will use for the sync.

If Airtable is not already connected, click Connect Airtable. You will be taken to Airtable’s authorization screen, where you can approve the bases and workspaces that Byteline is allowed to access.

After the connection is complete

  1. Select the Airtable base you want to use.
  2. Complete any additional setup required for the other app.
  3. Click Continue – Match your data.

Step 8: Choose and map your data

In this step, you will choose which tables should be synced and how their fields should be matched.

Review the table mapping

Byteline automatically suggests table mappings based on table names and the data available in each app.

Review the suggested mapping before continuing. To change the selected table or its settings, click More, and then select Edit table settings.

Review the field mapping

After a table is selected, Byteline automatically suggests mappings between fields that appear to contain similar information.

The field mapping is initially shown in a collapsed view. Click Show field matching to review the complete mapping.

From the detailed field-mapping view, you can:

  • Review the automatically matched fields.
  • Change an existing field mapping.
  • Remove a mapping that you do not need.
  • Click Add mapping to include additional fields.
  • Review the direction in which each field will be synchronized, when applicable.

Make sure important fields are mapped correctly before continuing. During the initial sync, mapped destination fields may be overwritten with values from the source app.

Step 9: Generate the sync preview

After reviewing the table and field mappings, click Continue.

Byteline will analyze the records in both apps and generate a preview showing how many records will be created, updated, or deleted.

No records are changed while the preview is being generated or reviewed. Changes begin only after you review the preview and start the sync.

Review the sync preview

When your sync includes existing data, Byteline shows a preview before the sync starts. The preview explains what will happen to your current records and how future changes will be handled.

Nothing is changed while you are reviewing the preview. Changes begin only after you select Start sync now.

A preview is not shown when you choose to sync future changes only, because no existing records will be added, updated, or deleted. In that case, you can start the sync directly.

When you start the sync

This section shows the changes Byteline will make during the initial sync of your existing data.

For each table or collection, you will see the number of records that will be:

  • Created: New records that will be added because they do not already exist in the destination.
  • Updated: Existing records that were matched and whose mapped fields will be overwritten with the latest values.
  • Deleted: Existing records that will be removed based on the delete behavior selected in your sync settings.

Expand a table or collection to review more information about the affected records. Pay particular attention to updates and deletes before starting the sync.

The summary also shows:

  • The number of records found in the source and destination.
  • How many matching keys were used to identify corresponding records.
  • Whether one side of the sync is read-only.
  • Which fields will be updated.

From then on, automatically

This section explains what will happen after the initial sync finishes and the sync becomes live.

Depending on the direction and settings you selected, Byteline can automatically:

  • Add newly created records to the other app.
  • Copy edits to the matching record.
  • Remove matching records when a record is deleted.

For a two-way sync, changes may move in either direction. For a one-way sync, changes move only from the source app to the destination app.

Review the sync settings

The Sync settings section provides a summary of your configuration, including:

  • Whether existing data, future changes, or both are included.
  • The number of tables or collections being synced.
  • The number of mapped fields.

Select Review full settings to see additional details. Select Edit settings when you need to change the sync configuration before starting.

After changing the settings, return to the preview and make sure the results are still what you expect.

Refresh the preview

The preview is based on the records and settings available when it was generated. The results may change when:

  • Records are added, edited, or deleted in either app.
  • You change field mappings, filters, matching rules, or delete behavior.
  • Some time has passed since the preview was generated.

Select Refresh preview to recalculate the creates, updates, and deletes using the latest data.

Start Sync

Once you have reviewed the preview and confirmed that the changes look correct, select Start sync now.

  1. Byteline will:
    • Perform an initial sync of your existing data.
    • Keep the sync running automatically, ensuring your Airtable data stays up to date.

You can monitor sync progress, view logs, or make changes anytime from the Syncs page. If you need to pause or edit the sync, simply open it from your dashboard.

✅ That’s it! Your Airtable sync is now live.

Airtable View Sync

You can sync data that is specific to an Airtable view, which is used to filter and organize your data. When you configure an Airtable data sync, Byteline requires a view to be specified. By selecting a specific view, only the relevant data contained within it will be synced. This applies to both historical syncing, for existing data, and ongoing synchronization.

You can configure a view during the sync creation as shown in the below screenshot.

⚠️ Limitation — When a View Filter Condition Is Not Based on Record Changes

When your Airtable sync is configured using a filtered view, most filters work perfectly because Airtable sends a webhook whenever a record is created, updated, or deleted — and Byteline Sync reacts immediately.

However, if your view includes conditions that can change without the record itself being modified, Airtable does not fire a webhook for those transitions. Examples include:

  • Filters using TODAY(), NOW(), or other time-based formulas

What happens in this case?

If a record stops matching the view due to one of these non-record-change conditions:

  • Airtable does not emit a webhook
  • Byteline does not receive a change event
  • The record quietly leaves the view, and therefore leaves the sync scope
  • The corresponding removal/update will not be applied in the destination app

Recommended Workarounds

You can use either of the following approaches to avoid this limitation.

Option 1: Use Byteline Sync Filters

Instead of using a filtered Airtable view to control which records are included in the sync, you can select an unfiltered Airtable view and configure the filtering conditions directly in Byteline.

For example, instead of creating an Airtable view that only includes records where:

  • Status is Active
  • Category is not Internal

you can configure the same conditions using Byteline Sync Filters.

This keeps the rules that determine which records participate in the sync directly within your Byteline sync configuration and avoids relying on Airtable view membership changes.

Recommended: If your Airtable view is mainly being used to control which records should be synced, consider using Byteline Sync Filters instead.

Option 2: Use a Helper Field in Airtable

If you prefer to continue using a filtered Airtable view:

  1. Add a helper field in Airtable, such as Sync Status or Active Today.
  2. Use an Airtable automation or other process to update that field when your condition becomes true or false.
  3. Use the helper field in your Airtable view filter.

Because the helper field is actually updated on the record, Airtable generates a change event that Byteline can detect and sync.

Creating missing select and multi-select options

Airtable select and multi-select fields can receive missing options automatically. See Automatically creating select options.

Airtable Permissions

You need to have Airtable Creator access to create a Byteline data sync.

Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive document will walk you through the step-by-step configuration process for Greenhouse data sync and address specific use cases tailored to Greenhouse.

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers usages of data sync features valid for all integrations.

Requirements

Installing app

  1. Go to Byteline Console.
  2. Create a new sync and choose Greenhouse as the first app. Then, select the second app.
  3. On the next screen, click Connect Greenhouse to establish a connection to your Greenhouse account.

Configuring Greenhouse Data Sync

Step 1: Start the Sync Setup

  1. Log in to your Byteline account and navigate to the My Syncs page.
  2. Click on the "Create Sync" button to begin the configuration.

Step 2: Select Greenhouse as Your First App

  1. Choose Greenhouse as the first app to sync.
    • Alternatively, you can select another app first and then pick Greenhouse as the second app.

Step 3: Connect the Second App

  1. Select the second app for syncing and log in to authorize the connection.
  2. Once connected, click "Continue" to move to the table mapping screen.

Step 4: Map Tables Between Greenhouse and the Other App

  1. Select the tables to sync between both apps.
  2. Select the tables you want to sync between the two apps.

Step 5: Choose Which Data to Sync

For each sync, you'll need to select whether to sync existing records, future changes, or both.

Step 6: Configure Field Mapping

  1. On the Field Mapping screen, drag and drop fields from the right panel into the mapped fields column to create mappings.Note: Not all fields are shown in the screenshot below.

  2. To delete a mapping, click the X button next to the field.
  3. Select the sync direction at the field level using the arrow buttons.One-Way Sync: Data flows from one app to the other.Two-Way Sync: Data flows bidirectionally between both apps.
  4. Once your mappings are finalized, click "Continue.

Step 7: Sync Existing Data Configuration

Select the sync direction for your existing data.

Step 8: Review Sync Preview

  1. Preview the sync setup to ensure everything is configured correctly.
  2. If all looks good, click "Start Sync."
  3. Byteline will:
    • Perform an initial sync of your existing data.
    • Keep the sync running automatically, ensuring your Greenhouse data stays up to date.

You can monitor sync progress, view logs, or make changes anytime from the Syncs page. If you need to pause or edit the sync, simply open it from your dashboard.

✅ That’s it! Your Greenhouse sync is now live.

How to Generate a Greenhouse Job Application Link

You can easily generate a Greenhouse job application link using the Job Post ID field available in your sync configuration. This link directs candidates straight to the job posting and application form.

The standard format is:

https://boards.greenhouse.io/<your_company_board>/jobs/<job_post_id>

✅ Example: If your company's greenhouse board is acme_company and the job post Id is 4900012345, the application link will be:

https://boards.greenhouse.io/acme_company/jobs/4900012345

This link can be shared directly with applicants or embedded on your careers page.

How to Find Your Greenhouse Job Board URL

To generate job application links, you’ll need your company’s Greenhouse job board URL (also called the board name). You can find it directly in your Greenhouse settings:

  1. Log in to your Greenhouse account.
  2. Click the Settings (⚙️) icon in the top navigation bar.
  3. From the left-hand menu, select Job Boards.
  4. In the Live Job Boards section, click the three dots (⋯) next to your active job board.
  5. Choose Edit Board Settings.
  6. On the settings page, you’ll see your Board Name, which is used in the job application URL.

Troubleshooting

Location and Offices are empty

A Greenhouse job post can still sync even if the Greenhouse user connected to Byteline does not have permission to view the underlying job.

The Location and Offices fields come from the job itself, not directly from the job post. If the connected Greenhouse user does not have access to the job, Greenhouse may return the job post while leaving Location and Offices empty.

To resolve this:

  1. In Greenhouse, give the user connected to Byteline access to the affected job, or
  2. Reconnect Greenhouse in Byteline using an account that has access to all jobs.

After updating the permissions, run the sync again.

No additional permission is required for the job post itself.

Updated
November 13, 2026
Excerpt is generated from the doc content.

Byteline lets you automatically sync Jobber clients, jobs, and invoices with Google Sheets and other supported apps.

You can import existing Jobber records, keep future changes synchronized, or configure a two-way sync so updates made in either app are reflected in the other. No coding or complex workflow automation is required.

This guide explains how to install Byteline Sync in Jobber and configure your first Jobber data sync.

What can you sync from Jobber?

Byteline supports the following Jobber data types:

Clients

Sync customer information from Jobber, including contact details and related client information.

Jobs

Sync Jobber jobs and work orders, including details such as assigned team members, timing, status, title, and customer information.

Invoices

Sync Jobber invoices, including invoice details, totals, payment status, line items, and related customer information.

Invoice Line Items

Sync individual line items from Jobber invoices, including descriptions, quantities, unit prices, and amounts. Each line item is synced as a separate record, making it easy to analyze invoice details, track services sold, and create detailed revenue reports in Google Sheets or other supported apps.

Visits

Scheduled visits and appointment details, including both recurring and non-recurring visits.

Requests

Requests in Jobber represent inquiries from potential or existing customers for services. They capture details such as customer information, requested services, and scheduling preferences, helping businesses track new opportunities before converting them into jobs.

Before you begin

You will need:

  1. An active Jobber account with permission to install apps.
  2. A Byteline account.
  3. Access to the app you want to connect to Jobber, such as Google Sheets.
  4. Permission to view or update the Jobber data included in your sync.

Standard Data Sync features

For information about features available across all Byteline integrations—including field mappings, filters, sync directions, previews, and issue resolution—see Data Sync - Getting Started

Installing Byteline Sync app in Jobber

Before configuring your sync, install the Byteline Sync app from the Jobber App Marketplace.

  1. Sign in to your Jobber account.
  2. Open Apps or the App Marketplace.
  3. Search for Byteline Sync.
  4. Select the Byteline Sync app.
  5. Click Connect.

  6. Review the requested permissions and approve access.

Create a Jobber data sync in Byteline

Step 1: Start a new sync

  1. Log in to your Byteline account and navigate to the My Syncs page.
  2. Click on the "Create Sync" button to begin the configuration.

Step 2: Select Jobber and your destination app. This document explains using Google Sheets. You can also use other apps such as Airtable.

  1. Choose Jobber as the first app to sync.
  2. Next, select the app you want to connect to Jobber, such as Google Sheets.

Step 3: Select the Jobber Data to Sync

Choose the types of Jobber data you want to sync to Google Sheets. You can select one or more of the following:

  • Jobs – Job details and status information.
  • Clients – Customer information and contact details.
  • Invoices – Invoice and billing information.
  • Requests – Customer service inquiries and requests.
  • Visits – Scheduled visits and appointment details.

Each selected data type creates a separate sync and a dedicated tab in your Google Sheets spreadsheet.

Once you've made your selections, click Continue to proceed with the setup.

Connect Google Sheets

After selecting the Jobber data you want to sync, you'll need to connect your Google account.

  1. Click Sign in with Google.
  2. Select the Google account you want to use.
  3. Follow the prompts to authorize Byteline to access Google Sheets.
  4. Once connected, click Next to continue.

Note: No data will be synced at this stage. You'll have a chance to review your selections before starting the sync.

Review & Start Syncing

Review the Jobber data types you've selected to sync with Google Sheets.

You can optionally change the Spreadsheet name or keep the default name, "Jobber data."

Click Start syncing to begin. Byteline will create a new Google Sheets spreadsheet with a separate tab for each selected data type and automatically keep your data up to date.

Syncing Your Jobber Data

After clicking Start syncing, you'll be taken to the Data Sync page, where you can monitor the progress of each sync.

Byteline starts syncing your selected Jobber data types one at a time.

  • Syncing existing data – Byteline is transferring existing Jobber records to Google Sheets. You can track the progress as a percentage.
  • Queued – The sync is waiting for the previous sync to finish its initial setup.
  • Live – The initial data sync is complete, and Byteline will automatically keep your Google Sheets data updated as changes occur in Jobber.

As each sync becomes Live, the next queued sync starts automatically. No further action is needed.

Your Jobber Syncs Are Live

Once the initial data transfer is complete, all your syncs will show a green Live status.

This means your Jobber data has been transferred to Google Sheets, and Byteline will automatically keep it updated as changes occur in Jobber.

You can open your Google Sheets spreadsheet to view your data, with a separate tab for each selected data type.

You're all set! No further action is required.

Customize Your Sync Settings

By default, Byteline creates your Jobber → Google Sheets syncs using recommended settings, so you can get started without additional configuration.

If you need more control, you can customize each sync individually.

For example, you can:

  • Choose fields – Select which Jobber fields to include or exclude from your Google Sheets sync.
  • Change sync direction – Configure how data flows between Jobber and Google Sheets.
  • Add filters – Choose which records should be synced based on specific conditions.
  • Adjust sync settings – Modify other settings to fit your needs.

To make changes, go to the Data Sync page, select the individual sync you want to customize, and edit its settings.

Each sync can be configured independently, allowing you to customize Jobs, Clients, Invoices, Requests, and Visits separately.

Monitor your Jobber sync

After the sync becomes live, open its details page to review:

  • Current sync status
  • Last successful sync time
  • Managed record count
  • Record-level sync history
  • Creates and updates
  • Sync warnings or errors
  • Sync settings and field mappings

Use the Issues section to review records that could not be synchronized and follow the displayed resolution instructions.

Frequently asked questions

Can I sync Jobber with Google Sheets?

Yes. Byteline can sync supported data with Google Sheets. You can import existing records, synchronize future changes, and configure one-way or two-way behavior where supported.

Can I export existing Jobber records?

Yes. Select Existing Data Only for a one-time export, or Existing Data and Future Changes to import existing records and keep them updated afterward.

Does the Jobber sync run automatically?

Yes. Byteline automatically checks for supported changes and synchronizes them according to your settings.

Can Google Sheets update Jobber?

Yes, when you configure a direction from Google Sheets to Jobber or choose a two-way sync. Only writable Jobber fields can be updated. Read-only fields are shown during field mapping.

Will connecting Jobber immediately change my data?

No. Connecting your account only authorizes access. Byteline does not begin modifying records until you review the preview and start the sync.

Can I change the mapped Jobber fields?

Yes. During setup, expand the field mapping to add, remove, or change fields. You can also edit the sync settings later. Changes to a live sync apply according to the options shown when editing.

Why can’t I update a particular Jobber field?

Some Jobber fields are read-only or cannot be changed through the Jobber API. Byteline identifies read-only fields in the mapping screen and prevents unsupported updates.

Need help with your Jobber integration?

Use the Chat option in the bottom-right corner of the Byteline console for assistance with choosing the right Jobber data type, configuring field mappings, reviewing the sync preview, or resolving sync issues.

Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive document will walk you through the step-by-step configuration process for Notion data sync and address specific use cases tailored to Notion.

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers usages of data sync features valid for all integrations.

Configuring Notion Data Sync

1. Click on the 'Add New' button

2. Pick the 'Notion' from dropdown.

3. Pick the app that you want to sync with Notion.

4. Select the 'Airtable base' from dropdown.

5. Click on 'Next' button

6. Delete any tables that you don't want to sync. If the table you want to sync is not displayed, add it using "Add table" button.

7. Click on 'Next' button.

8. Delete any fields that you don't want to sync. If the field you want to sync is not displayed, add it using "Add field" button.

9. Click on 'Save' button

10. Carefully review the number of creates, updates, and deletes. Then click "Start Sync". If the numbers are not correct, it means your unique key selection needs to be changed.

Notion Page Content

Every Notion database record has a corresponding page content that can be synced. Byteline uses pageContent field to represent the HTML content of a Notion page. Take a look at the screenshot below to see an example of the latter:

This read-only field can be synced from Notion to other apps by easily mapping from the data sync screens, shown below.

Handling Automatic Updates in Notion Pages with Linked Relationships

Byteline relies on the last_edited_time property to detect changes in Notion pages. However, Notion has a limitation where the last_edited_time is not updated if a page is automatically changed due to relationships linked to the same table. For instance, if you modify one record, such as Parent, the change might automatically update a related record, such as Child, because of the parent-child relationship. Despite this, the last_edited_time of the automatically updated record remains unchanged, making it undetectable by Byteline.

Solutions

  1. Manually Update a ColumnEdit any column in your autmmatically changed Notion page (record) manually to ensure the last_edited_time is updated. This action makes the record detectable by Byteline. You can introduce a dedicated column in your Notion database specifically for this purpose.
  2. Notion AutomationUse automation in Notion to ensure that automatically updated records also have their modification date updated. This ensures that Byteline can detect and sync these changes seamlessly.

By implementing these solutions, particularly automation, users have resolved this issue, allowing Byteline to detect and synchronize modified records without any problems.

Supported Notion Page Fields

The following Notion page fields are fully supported.

Notion Page FieldSupportedComments
Richtext✅
To-do list✅Displayed as either checked or unchecked checkbox, based on the value.
Bulleted list✅
Numbered list✅
Quote✅
Image✅
Video (YouTube & Wistia)✅
Audio embed (Spotify)✅
Code✅
Bookmark✅
Table✅

Creating missing select and multi-select options

Notion select and multi-select fields can receive missing options automatically. See Automatically creating select options.

Troubleshooting

My Notion Table Doesn't Show Up in the Dropdown

If you've created a table in Notion but don't see it listed in the dropdown when setting up your sync, here's what's likely happening:

🚫 The Table Isn't a Database Yet

In Notion, you can create something that looks like a table, but it may not actually be a database. Our dropdown only shows Notion databases, because those are what support syncing.

If your table was added using the “/table” command or the + menu, it may just be a regular table, not a database.

✅ How to Fix It

You need to convert your table into a database in Notion:

  1. Open the page in Notion where your table was created.
  2. Click the three dots at the top-right corner of the table. Click "Turn into database".

  3. Return to the dropdown and refresh — your database should now appear in the list.
Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive guide walks you through the step-by-step configuration process for syncing Webflow eCommerce data using Byteline.

Supported Data Types

Byteline currently supports syncing the following Webflow eCommerce data objects:

  • Products (including SKUs)
  • Orders

Syncing Webflow CMS Data

If you're looking to sync data with Webflow CMS (such as blog posts, authors, or other CMS collections), the setup process is different from Webflow eCommerce.

➡️ Please follow the instructions in the Webflow CMS Data Sync for detailed steps.

This guide is specifically focused on syncing Webflow eCommerce data, such as Products and Orders.

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers the usage of data sync features valid for all integrations.

Setting up Webflow eCommerce Data Sync with Byteline

Follow these steps to configure data sync for Webflow eCommerce Products using Byteline. You can follow a similar process to sync Webflow eCommerce Orders.

Step 1: Start the Sync Setup

  1. Log in to your Byteline account and navigate to the My Syncs page.
  2. Click on the "Create Sync" button to begin the configuration.

Step 2: Select Webflow as Your First App

  1. Choose Webflow as the first app to sync.Alternatively, you can select another app first and then pick Webflow as the second app.
  2. Click on the "Sign In" button, if not already connected, under Webflow to connect it to Byteline.
  3. Now select the eCommerce - Product for the data type to sync.
  4. Select the site for which the data needs to be synced.

Step 3: Connect the Second App

  1. Select the second app for syncing and log in to authorize the connection.
  2. Once connected, click "Continue" to move to the table mapping screen.

Step 4: Map Tables Between Webflow eCommerce and the Other App

Note: In the instructions below, Webflow is configured as the right-side app in the sync setup.

This means you’ll be mapping fields from the other app (left side) to the corresponding fields in Webflow eCommerce (right side).

  1. Select the tables you want to sync between the two apps.

Step 5: Choose Which Data to Sync

For each sync, you'll need to select whether to sync existing records, future changes, or both.

  • Products:Choose "Existing Data and Future Changes" to sync all current product data to Webflow, along with any future updates.If products already exist in Webflow, Byteline will only sync the differences, avoiding duplicate entries.
  • Orders:Typically, select "Future Changes Only" so that new orders are synced to your connected app as they are placed.

Step 6: Configure Field Mapping

  1. On the Field Mapping screen, drag and drop fields from the right panel into the mapped fields column to create mappings.

  2. To delete a mapping, click the X button next to the field.
  3. Select the sync direction at the field level using the arrow buttons.One-Way Sync: Data flows from one app to the other.Two-Way Sync: Data flows bidirectionally between both apps.
  4. Once your mappings are finalized, click "Continue.

Step 7: Sync Existing Data Configuration

Select the sync direction for your existing data.

Step 8: Review Sync Preview

  1. Preview the sync setup to ensure everything is configured correctly.
  2. If all looks good, click "Start Sync."
  3. Byteline will sync your existing data and make the sync live.

Additional Configuration

Products That Do Not Require Shipping

When syncing products to Webflow eCommerce, you must configure the Requires Shipping field appropriately.

  • If this field is not mapped, Webflow will assume the product requires shipping.
  • To ensure that products like digital goods or services do not require shipping, you must explicitly map the Requires Shipping field and set its value to false.

This is important to avoid shipping-related issues for non-physical products.

Webflow’s 50-Variant Limit

Webflow enforces a strict limit of 50 variants per product. This is a platform-level restriction and cannot be overridden by Byteline.

A product’s total variants are calculated by multiplying all option values. For example:

  • 3 sizes × 10 colors = 30 variants → Allowed
  • 6 sizes × 10 colors = 60 variants → Rejected by Webflow

If a product exceeds 50 variants, Webflow will not allow it to be created or updated, and the sync will fail.

Recommendation: Before syncing multi-variant products to Webflow, ensure the total number of variants in the paired app, such as Printful, does not exceed 50. If necessary, reduce the number of sizes, colors, or other option values in your source product to comply with Webflow’s limitation.

Troubleshooting Webflow eCommerce Products

Product not found while adding variants

Error: Product not found. This can sometimes happen if the data sync ran into an issue while adding the product.

This error can occur while syncing product variants to Webflow when the parent product was not successfully created during an earlier sync.

Because variants are always linked to a product, Webflow cannot accept a variant unless its product already exists. If the product failed to sync, any attempt to add or update its variants will result in this error.

Why this happens

  • The data sync encountered an error while creating the Webflow Product
  • The product record is missing in Webflow
  • Variants tried to sync before the product was successfully added - FIX

How to resolve the issue

Follow these steps to fix the problem in the correct order.

1. Find products that failed to sync

Use the Record Change History to identify product-level errors.

Apply the following filters:

  • Destination Table: Webflow Product
  • Status: Error

This will show all product records that failed to sync to Webflow.

2. Fix the product sync error

  • Open each failed product record
  • Review the error reason
  • Fix the underlying issue (for example: missing required fields, invalid values, or configuration issues)
  • Resync the product so it is successfully created in Webflow
⚠️ Variants cannot be added until the product exists in Webflow.

3. Resync the product variants

Once the product is successfully synced:

  • Go back to the variant record(s)
  • Run Resync on the variant

The variant sync should now succeed since the product is available.

Key takeaway

Always resolve product-level errors first. Variant errors like “Product not found” are usually a downstream effect of a failed product sync.

If you continue to see issues after resyncing the product, please reach out to Byteline support with the error details.

Product variant shows quantity 0 in Webflow

When syncing products to Webflow eCommerce, some product variants may appear in Webflow with Quantity set to 0.

This usually means the variant is unavailable in the source app. Byteline translates unavailable product variants into Webflow by setting their inventory quantity to 0.

For example, if you sync a product from Printful and a specific size, such as XS, is not available for that product, the matching Webflow variant is synced with quantity 0.

This is expected behavior. In Webflow eCommerce, unavailable variants are represented as out of stock by setting the quantity to 0.

Why this happens

  • The variant exists as part of the product option combination.
  • The matching variant is unavailable in the source app.
  • Byteline syncs this unavailability to Webflow by setting the variant quantity to 0.

Key takeaway

A Webflow quantity of 0 does not always mean the sync failed. It can simply mean the variant is unavailable in the source app, and Byteline has correctly synced that unavailability to Webflow.

Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive guide walks you through the step-by-step configuration process for syncing Printful data using Byteline.

Supported Data Types

Byteline currently supports syncing the following Printful data objects:

  • Products (including variants)
  • Orders

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers usages of data sync features valid for all integrations.

Creating a Printful Store to Use with Byteline

  1. Log in to your Printful account and navigate to the Stores section.
  2. Click on Add Store, then locate the Manual order platform / API box.
  3. Inside that box, click the "Connect via API" button to create a new store that can integrate with Byteline.

Migrating Your Printful Store to a “Manual Order Platform / API” Store

Byteline can only connect to Printful stores created under the “Manual order platform / API” type. If your current Printful store is connected to another platform (like Shopify, Etsy, or WooCommerce), you’ll need to migrate your products to a “Manual order platform / API” store before using Byteline.

The good news is that Printful makes this process simple — you can duplicate your existing products in bulk (if supported by your store) and publish them to the new store type.

Follow the steps below to complete the migration. All actions are performed within your Printful Dashboard, and the process must be repeated for each product you wish to migrate.

Steps to Migrate Your Products

  1. Create a “Manual order platform / API” store (if you don’t have one yet)
    • In your Printful Dashboard -> Stores, click “Connect via API” to create a new store.
    • This new store will be used for Byteline integration.

  2. Open your existing store’s products
    • From the left sidebar, navigate to Stores.
    • Locate the store containing the products you want to migrate and click View products.
  3. Duplicate products to templates
    • If your store supports the Bulk edit option, you can duplicate all products to templates in a single action:
      • Click Bulk edit

      • Select all the products you want to export.
      • Click "Duplicate to templates" to create templates for all selected products at once.

    • If your store does not support Bulk edit, you’ll need to duplicate products individually:
      • For each product, click the three vertical dots (⋮) next to it and select Duplicate to templates.

    • This saves your product design as a reusable template.
  4. Publish templates to your new store
    • Go to the Product templates tab.

    • Find the duplicated templates, select all that you want to copy to the new store.
    • Click the Publish button at the top of the product templates list.

Once all products are published to your “Manual order platform / API” store, you can connect it to Byteline and start syncing products to other platforms — such as Webflow eCommerce or any other supported app.

Installing app

  1. Log in to the Byteline Console
  2. Create a new sync and select Printful as one of the apps.
  3. Click the Sign in button under the Printful app.

  4. In the Printful connection dialog, select your store and click Authorize.

  5. Once you see the success message, your Printful connection is complete.

Configuring Printful Data Sync

Step 1: Start the Sync Setup

  1. Navigate to the My Syncs page.
  2. Click the "Create Sync" button.
  3. Choose Printful as the first app, or as the second app after selecting another app first.

Step 2: Choose Printful Data Type

  1. Select the Printful data type you wish to sync. You can select any supported data type.

    This section shows the steps for Printful products, but the steps are applicable to any data type.

  2. After selecting the data type, choose the details for the paired app and click Continue to proceed to table mapping.

Step 3: Map Tables Between Printful and the Other App

Byteline products provide two tables for products:

  • Products
  • Product Variant

To fully sync your Printful catalog, you should sync both tables.

Step 4 - Select Which Data to Sync

  • Products: Choose Existing data and future changes to sync your entire catalog.
  • Orders: Typically, choose Future changes only to sync new incoming orders.

Step 5: Configure Field Mapping

  1. On the Field Mapping screen, drag and drop fields from the right panel into the mapped fields column to create mappings.
  2. Perform the field mapping for both tables

  3. To delete a mapping, click the X button next to the field.
  4. Select the sync direction at the field level using the arrow buttons.ProductsOrders
    • Printful is the source of truth.
    • Sync direction is from Printful to the other app (default and unchangeable).
    • Printful is typically the target for incoming orders.
    • Sync direction is from the other app (e.g., Foxy) to Printful.
  5. Once your mappings are finalized, click "Continue."

Step 6: Configure Sync for Existing Data (if applicable)

This step is shown only when the historical sync is selected in the data to sync. Pick the sync direction for your existing data.

Step 8: Review Sync Preview

  1. Preview the sync setup to ensure everything is configured correctly.
  2. If all looks good, click "Start Sync."
  3. Byteline will sync your existing data and make the sync live.

Step 9: Automatic Record Syncing

Once the sync is live, any changes made to records in either app will automatically sync to the other app in real-time.

Why Use Byteline for Printful Data Sync?

Byteline simplifies the process of syncing data between Printful and other apps, ensuring:

  • Real-time data synchronization.
  • Easy-to-use field mapping and sync direction configuration.
  • Quick, no-code setup

⚠️ Important: Webhook Limitation in Printful

Printful allows only one active webhook URL per store. This limitation has a direct impact on Byteline Data Sync functionality.

If you connect your Printful store to another product or service that sets up its own webhook, it will overwrite the webhook configured by Byteline, which is essential for detecting and syncing changes in your products.

As a result, any changes made to your Printful store will no longer be picked up by Byteline, and your sync may stop functioning correctly.

📄 From Printful’s Official Documentation:

“Note that only one webhook URL can be active for a store, so calling this method disables all existing webhook configuration.” — Printful Webhook API Documentation

Recommendation:

To ensure continued and reliable syncing with Byteline, do not connect your Printful store to other systems that use webhooks

What Printful Stores Are Supported?

Byteline supports syncing only specific types of Printful stores based on API availability.

✅ Supported Stores

The following store types are supported:

  • Manual order platform / API

These stores provide API access from Printful, which allows Byteline to:

  • Fetch products and variants
  • Sync data with other apps
  • Create and manage orders

❌ Unsupported Stores

The following store types are not supported:

  • Quick Stores
  • Platform-connected stores, including:
    • Shopify
    • Etsy
    • Squarespace
    • Amazon
    • Other eCommerce platform integrations

These stores are not supported because Printful does not expose the required API access for third-party syncing tools like Byteline.

Troubleshooting

Switch to a Printful store based on the Manual Order/API platform

Byteline can only connect to Printful stores created using the Manual order platform / API option. Stores connected to platforms like Shopify or Etsy are restricted to those specific platforms and cannot be used with Byteline.

To resolve this, create a new Printful store using the Manual order platform / API option. For step-by-step instructions, see the section above: Creating a Printful Store to Use with Byteline.

Sync Has Stopped Working

Possible Cause:

If your Printful sync suddenly stops working, it's likely that the webhook configured by Byteline was overwritten by another service connected to your store.

For more details, see the Webhook Limitation in Printful section above.

How to Fix It:

  • Reconnect your Printful store to Byteline by going to the Connections page and clicking "Reauthorize Connection".
  • Avoid connecting other platforms that may overwrite the webhook.
Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive document will walk you through the step-by-step configuration process for Supabase data sync and address specific use cases tailored to Supabase.

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers usages of data sync features valid for all integrations.

Requirements

Installing app

  1. Go to Byteline Console.
  2. Create a new sync and choose Supabase as the first app. Then, select the second app.
  3. On the next screen, click Connect Supabase to establish a connection to your Supabase account.

Configuring Supabase Data Sync

Step 1: Start the Sync Setup

  1. Log in to your Byteline account and navigate to the My Syncs page.
  2. Click on the "Create Sync" button to begin the configuration.

Step 2: Select Supabase as Your First App

  1. Choose Supabase as the first app to sync.
    • Alternatively, you can select another app first and then pick Supabase as the second app.

Step 3: Connect the Second App

  1. Select the second app for syncing and log in to authorize the connection.
  2. Once connected, click "Continue" to move to the table mapping screen.

Step 4: Map Tables Between Supabase and the Other App

  1. Select the tables to sync between both apps.
  2. Select the tables you want to sync between the two apps.

Step 5: Choose Which Data to Sync

For each sync, you'll need to select whether to sync existing records, future changes, or both.

Step 6: Configure Field Mapping

  1. On the Field Mapping screen, drag and drop fields from the right panel into the mapped fields column to create mappings.Note: Not all fields are shown in the screenshot below.

  2. To delete a mapping, click the X button next to the field.
  3. Select the sync direction at the field level using the arrow buttons.One-Way Sync: Data flows from one app to the other.Two-Way Sync: Data flows bidirectionally between both apps.
  4. Once your mappings are finalized, click "Continue.

Step 7: Sync Existing Data Configuration

Select the sync direction for your existing data.

Step 8: Review Sync Preview

  1. Preview the sync setup to ensure everything is configured correctly.
  2. If all looks good, click "Start Sync."
  3. Byteline will:
    • Perform an initial sync of your existing data.
    • Keep the sync running automatically, ensuring your Supabase data stays up to date.

You can monitor sync progress, view logs, or make changes anytime from the Syncs page. If you need to pause or edit the sync, simply open it from your dashboard.

✅ That’s it! Your Supabase sync is now live.

What Byteline Adds to Your Supabase Database

Record ID Handling in Supabase

For Byteline to reliably track and sync records, each row in a Supabase table must have a unique identifier (Record ID). Byteline determines the Record ID using the following logic:

Using an Existing Primary Key (Recommended)

If your Supabase table already has a primary key column, Byteline will automatically use that column as the Record ID.

  • This is the preferred approach.
  • Works seamlessly with standard Supabase schemas.
  • Ensures consistency with your existing database design.

Auto-Generated Record ID (When No Primary Key Exists)

If no primary key is defined on the table, Byteline will automatically add a new column:

byteline_row_id

  • Type: UUID
  • Automatically generated for each row
  • Managed by Supabase (as part of the table schema)
  • Used internally by Byteline as the unique Record ID

Important Notes

  • The byteline_row_id column is only created when no primary key exists.
  • Once created, it becomes the permanent identifier for records in that table.
  • You should avoid modifying or deleting this column, as it is required for sync consistency.
  • If you later add your own primary key, existing syncs will continue using byteline_row_id unless you restart the Byteline sync.

Functions and triggers

To securely connect your Supabase data and keep it in sync, Byteline adds three small helpers to your database.

These helpers are safe, lightweight, and do not change your existing data.

  1. byteline_get_tablesThis function lets Byteline see a list of tables in your database.Why Byteline needs itWhen you’re setting up a sync, Byteline needs to show you which tables are available so you can choose the right one.What it can accessImpact on your database
    • Table names only
    • No rows
    • No actual data
    • Read-only
    • No performance impact
    • Does not modify anything
  2. byteline_get_table_columnsThis function retrieves the fields (columns) inside a selected table, along with their data types.Why Byteline needs itByteline uses this information to:What it can accessImpact on your database
    • Show available fields during setup
    • Help you map fields correctly
    • Prevent data type mismatches
    • Column names (for example: email, created_at)
    • Data types (text, number, date, etc.)
    • No row data
    • Read-only
    • No access to your actual records
  3. byteline_{table_id}_change_triggerThis trigger notifies Byteline whenever data changes in a specific table.Why Byteline needs itIt allows Byteline to:When a row is added, updated or deleted, Supabase sends a small notification to Byteline so it knows something changed.What it does not do
    • Detect new or updated records instantly
    • Keep your data in sync without delays
    • Avoid constant polling or manual refreshes
    • It does not send your full data automatically
    • It does not change or block updates
    • It does not slow down your database

Important Notes

  • ✅ Byteline does not modify your existing data or tables
  • ✅ Byteline only works with the tables you explicitly select
  • ⚠️ These functions and triggers are required for syncing to work properly
  • ⚠️ If they are removed while connected, Byteline will no longer be able to sync your data
  • 🔧 You can disconnect Supabase from Byteline at any time, and then safely delete these helpers from Supabase if you no longer need them

Using Non-public Schemas

By default, Supabase exposes the public schema for API access. If you choose to sync data from a non-public schema, additional database privileges are required for Byteline to operate correctly.

When a non-public schema is selected, Byteline automatically verifies whether the required permissions already exist. If they do not, Byteline securely applies the necessary grants on your behalf — no manual SQL execution is required.

This is done purely for convenience and to ensure the sync works out of the box.

What permissions are granted (and why)

Byteline requests only the minimum privileges required to support data sync functionality:

  • List tables in the schema
  • Perform full CRUD operations (Create, Read, Update, Delete)
  • Create and execute functions (including trigger functions)
  • Add change triggers to tables so updates can be detected reliably

No unrelated or broad permissions are granted.

Automatically applied privilege script

When needed, Byteline applies a schema-scoped permissions script similar to the following (shown here for transparency):

GRANT USAGE, CREATE ON SCHEMA '<schema>' TO service_role;

GRANT SELECT, INSERT, UPDATE, DELETE, TRIGGER
ON ALL TABLES IN SCHEMA '<schema>' TO service_role;

GRANT USAGE, SELECT, UPDATE
ON ALL SEQUENCES IN SCHEMA '<schema>' TO service_role;

GRANT EXECUTE
ON ALL FUNCTIONS IN SCHEMA '<schema>' TO service_role;

GRANT USAGE ON LANGUAGE plpgsql TO service_role;

ALTER DEFAULT PRIVILEGES IN SCHEMA '<schema>'
GRANT SELECT, INSERT, UPDATE, DELETE, TRIGGER ON TABLES TO service_role;

ALTER DEFAULT PRIVILEGES IN SCHEMA '<schema>'
GRANT USAGE, SELECT, UPDATE ON SEQUENCES TO service_role;

ALTER DEFAULT PRIVILEGES IN SCHEMA '<schema>'
GRANT EXECUTE ON FUNCTIONS TO service_role;

  • These grants are schema-specific and do not affect other schemas.
  • The script is executed only if required permissions are missing.
  • Existing permissions are respected and never overridden.
  • This uses Supabase’s service_role, which is already designed for trusted backend operations.

This approach allows you to use custom schemas safely while keeping your Supabase setup clean, secure, and low-friction.

Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive document will walk you through the step-by-step configuration process for Webflow data sync and address specific use cases tailored to Webflow.

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers usages of data sync features valid for all integrations.

Syncing Webflow eCommerce Data

If your goal is to sync Webflow eCommerce data—such as Products or Orders—this guide does not apply, as the configuration differs from CMS collections.

➡️ Please refer to the Webflow eCommerce Data Sync for detailed instructions.

This document specifically covers syncing Webflow CMS collections like blog posts, team members, and other custom content.

Configuring Webflow Data Sync

1. Click "Add new" to create a new sync.

2. Pick the app that you want to sync with Webflow.

3. Pick Webflow and select the site to sync. Note: The order doesn't matter; you can choose Webflow as the first or second app.

4. Click "Next"

5. Delete any tables that you don't want to sync. If the table you want to sync is not displayed, add it using "Add table" button.

6. Click "Next"

7. Now configure your field mappings. Click "Add field" to add any fields that are not shown by default.

Tip! Historical syncs your existing data. This functionality works based on the unique keys. So pay close attention to the selected keys (in green) to ensure they are unique. You can select multiple keys.

8. Click "Save"

9. Carefully review the number of creates, updates, and deletes. Then click "Start Sync". If the numbers are not correct, it means your unique key selection needs to be changed.

Syncing Webflow items as draft

Let's explore the process of saving synchronized Webflow items as drafts. This can be achieved by mapping the "Draft" Webflow column to a corresponding boolean or checkbox column in your other chosen application. Once the mapping is complete, set the value of this column in the other app to "true" or "checked" for all rows.

Restoring Webflow backup

Byteline's data sync stores Webflow item IDs for its sync logic. But when a Webflow backup is restored, the IDs of the Webflow items change, and as a result, the data sync will run into unexpected behavior. So please follow the below steps to restore a Webflow site when using Byteline's data sync for the site.

  1. Stop Byteline's data sync
  2. Restore the Webflow site from its backup
  3. Start Byteline's data sync.

Syncing Multilingual Content

If your source app stores content in separate language fields (for example: Title_EN, Title_FR, Title_DE), you can map each field normally during sync.

See Multilingual Content Support for full details.

Troubleshooting

Items Not Automatically Published

Using the Webflow designer or editor, check if any collection items have a status other than "Published." If you do find any such items, this could be the reason why certain records are not synchronizing in the Published state. In these cases, the live update from Byteline may fail.

To resolve this issue, ensure all items are set to the "Published" status within your Webflow site to resolve this issue. You can either publish your Webflow site or non-published items to update the status. Once you've done this, your items should automatically be published for ongoing sync changes.

Expected value to be a single line

You need to change the Webflow CMS field to allow multiple lines. It can easily be done by following the below steps:

  • Go to the Webflow designer -> CMS.
  • Hover over the collection and click on the settings icon.
  • Select the field for which the error is generated and hit the "Multiple line" radio button. Then click on the "Save Field" button.

Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive guide walks you through the step-by-step configuration process for syncing Foxy data using Byteline.

Supported Data Types

Byteline currently supports syncing the following Foxy data objects:

  • Customers
  • Transactions

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The Getting Started document covers the usage of data sync features that are valid for all integrations.

Setting up Foxy Data Sync with Byteline

Follow these steps to configure data sync for Foxy Transactions using Byteline. You can follow a similar process to sync other Foxy data types.

Step 1: Start the Sync Setup

  1. Log in to your Byteline account and navigate to the My Syncs page.
  2. Click on the "Create Sync" button to begin the configuration.

Step 2: Select Foxy as Your First App

  1. Choose Foxy as the first app to sync.Alternatively, you can select another app first and then pick Foxy as the second app.
  2. Click on the "Connect Foxy" button, if not already connected, under Foxy, to connect it to Byteline.
  3. Now select the Transaction for the data type to sync.

Step 3: Connect the Second App

  1. Select the second app for syncing and connect to authorize the connection.
  2. Once connected, click "Continue" to move to the table mapping screen.

Step 4: Map Tables Between Foxy Transaction and the Other App

Note: Foxy transactions is a read-only connector, meaning it can only act as the source in a sync.

  1. Select the tables you want to sync between the two apps.

    Foxy transactions include a Record Tracking Time Frame feature, which lets you define how long a transaction should be monitored. For example, if your transactions typically remain unchanged after 3 months, you can set the tracking time frame to 3 months.Once the specified time has passed, the transaction is no longer managed or included in billing. Any updates made to the record after this period will be ignored by Byteline

Step 5: Choose Which Data to Sync

For each sync, you'll need to select whether to sync existing records, future changes, or both. When syncing transactions, the most common choice is to sync future changes only.

Step 6: Configure Field Mapping

  1. On the Field Mapping screen, drag and drop fields from the right panel into the mapped fields column to create mappings.

  2. To delete a mapping, click the X button next to the field.
  3. Select the sync direction at the field level using the arrow buttons.One-Way Sync: Data flows from one app to the other.Two-Way Sync: Data flows bidirectionally between both apps.
  4. Once your mappings are finalized, click "Continue.

Step 7: Start the Sync

Click Start Sync at the bottom of the field mapping section to activate your sync. From this point on, any transaction processed in Foxy will automatically be sent to Wix orders (as shown in this guide’s example).

You can monitor sync progress, view logs, or make changes anytime from the Syncs page. If you need to pause or edit the sync, simply open it from your dashboard.

✅ That’s it! Your Foxy sync is now live.

Use Case: Inventory Sync with Wix

When you sync Foxy transactions with Wix orders, your Wix product catalog inventory is automatically updated. To enable this, the code field in Foxy transaction line items must be mapped to the SKU value. This setup is handled in your Foxy account. If you need help configuring it, please reach out to Foxy customer support.

Updated
November 13, 2026
Excerpt is generated from the doc content.

Byteline supports syncing multilingual content across all connectors.

Syncing Multiple Language Fields

If your source app stores content in separate fields for different languages (for example: Title_EN, Title_FR, Title_DE), you can map each field to a corresponding field in your destination app.

Byteline treats language-specific fields like any other field during sync.

  • No special configuration required
  • Full UTF-8 support
  • Works with all languages (including accented and non-Latin characters)
  • Platform-Level Localization FeaturesSome apps (such as Webflow) offer native localization systems with separate locale-based content structures.Byteline syncs standard fields. If you are using a platform’s native localization system, behavior may depend on how that platform exposes its content via API.If you're unsure about your setup, contact support and we’ll guide you.
Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive guide walks you through the step-by-step configuration process for syncing Stripe data using Byteline.

Supported Data Types

Byteline currently supports syncing the following Stripe data objects:

  • Customer
  • Invoice
  • Subscription
  • Payment

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The Getting Started document covers data sync features that are valid for all integrations.

Setting up Stripe Data Sync with Byteline

Follow these steps to configure data sync for Stripe Customers using Byteline. You can follow a similar process to sync other Stripe data types.

Step 1: Start the Sync Setup

  1. Log in to your Byteline account and navigate to the My Syncs page.
  2. Click on the "Create Sync" button to begin the configuration.

Step 2: Select Stripe as Your First App

  1. Choose Stripe as the first app to sync.Alternatively, you can select another app first and then pick Stripe as the second app.
  2. Click on the "Sign In" button, if not already connected, under Stripe, to connect it to Byteline.
  3. Now select the Customer for the data type to sync.

Step 3: Connect the Second App

  1. Select the second app for syncing and log in to authorize the connection.
  2. Once connected, click "Continue" to move to the table mapping screen.

Step 4: Map Tables Between Stripe and the Other App

  1. Select the tables you want to sync between the two apps.

Step 5: Choose Which Data to Sync

For each sync, you'll need to select whether to sync existing records, future changes, or both.

Step 6: Configure Field Mapping

  1. On the Field Mapping screen, drag and drop fields from the right panel into the mapped fields column to create mappings.

  2. To delete a mapping, click the X button next to the field.
  3. Select the sync direction at the field level using the arrow buttons.One-Way Sync: Data flows from one app to the other.Two-Way Sync: Data flows bidirectionally between both apps.
  4. Once your mappings are finalized, click "Continue.

Step 7: Sync Existing Data Configuration

Select the sync direction for your existing data.

Step 8: Review Sync Preview

  1. Preview the sync setup to ensure everything is configured correctly.
  2. If all looks good, click "Start Sync."
  3. Byteline will:
    • Perform an initial sync of your existing data.
    • Keep the sync running automatically, ensuring your Stripe data stays up to date.

You can monitor sync progress, view logs, or make changes anytime from the Syncs page. If you need to pause or edit the sync, simply open it from your dashboard.

✅ That’s it! Your Stripe sync is now live.

Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive document will walk you through the step-by-step configuration process for Framer data sync and address specific use cases tailored to Framer.

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers usages of data sync features valid for all integrations.

Requirements

Installing app

  1. Go to Byteline Console.
  2. Create a new sync and choose Framer as the first app. Then, select the second app.
  3. On the next screen, click Connect Framer to establish a connection to your Framer account.

    How to get your Framer API Key

    1. Log in to your Framer account
    2. Select the project you want to connect
    3. Open Site Settings → General
    4. Scroll to the API Keys section
    5. Click Create API Key
    6. Copy the generated key and paste it here. (The API key in the UUID format, e.g. c54d76df-05b0-43a3-ab2d-80cdf6757e48)Important: Make sure you generate the API key for the correct site, as each site has its own key.

    How to find your Framer Project ID

    1. Open your Framer project in the browser.
    2. Look at the URL in the address barExample: https://framer.com/projects/Nova-App-copy--dFu2XRqmWggPa1234567-1BR5X?node=...
    3. The Project ID is the string after the project name and -. You only need the part before the next after the -.In this example:Project ID = dFu2XRqmWggPa1234567

Configuring Framer Data Sync

Step 1: Start the Sync Setup

  1. Log in to your Byteline account and navigate to the My Syncs page.
  2. Click on the "Create Sync" button to begin the configuration.

Step 2: Select Framer as Your First App

  1. Choose Framer as the first app to sync.

    • Alternatively, you can select another app first and then pick Framer as the second app.

Step 3: Connect the Second App

  1. Select the second app for syncing and log in to authorize the connection.
  2. Once connected, click "Continue" to move to the table mapping screen.

Step 4: Map Tables Between Framer and the Other App

  1. Select the tables to sync between both apps.
  2. Select the tables you want to sync between the two apps.

Step 5: Choose Which Data to Sync

For each sync, you'll need to select whether to sync existing records, future changes, or both.

Step 6: Choose Sync Direction

For a two-way sync, select the two-way option and then choose the direction for syncing existing data. For a one-way sync, the direction for real-time and historical sync remains the same.

Step 7: Configure Field Mapping

  1. On the Field Mapping screen, drag and drop fields from the right panel into the mapped fields column to create mappings.Note: Not all fields are shown in the screenshot below.

  2. To delete a mapping, click the X button next to the field.
  3. Select the sync direction at the field level using the arrow buttons.One-Way Sync: Data flows from one app to the other.Two-Way Sync: Data flows bidirectionally between both apps.
  4. Once your mappings are finalized, click "Continue.

Step 8: Review Sync Preview

  1. Preview the sync setup to ensure everything is configured correctly.

  2. If all looks good, click "Start Sync."
  3. Byteline will:
    • Perform an initial sync of your existing data.
    • Keep the sync running automatically, ensuring your Framer data stays up to date.

You can monitor sync progress, view logs, or make changes anytime from the Syncs page. If you need to pause or edit the sync, simply open it from your dashboard.

✅ That’s it! Your Framer sync is now live.

Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive guide walks you through the step-by-step configuration process for syncing Wix data using Byteline.

Supported Data Types

Byteline currently supports syncing the following Wix data objects:

  • CMS
  • Orders
  • Events
  • Contacts
  • Members

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The Getting Started document covers the usage of data sync features that are valid for all integrations.

Setting up Wix Data Sync with Byteline

Follow these steps to configure data sync for Wix CMS using Byteline. You can follow a similar process to sync other Wix data types.

Step 1: Start the Sync Setup

  1. Log in to your Byteline account and navigate to the My Syncs page.
  2. Click on the "Create Sync" button to begin the configuration.

Step 2: Select Wix as Your First App

  1. Choose Wix as the first app to sync.Alternatively, you can select another app first and then pick Wix as the second app.
  2. Click on the "Sign In" button, if not already connected, under Wix, to connect it to Byteline.
  3. Now select the CMS for the data type to sync.

Step 3: Connect the Second App

  1. Select the second app for syncing and log in to authorize the connection.
  2. Once connected, click "Continue" to move to the table mapping screen.

Step 4: Map Tables Between Wix CMS and the Other App

Note: In the instructions below, Wix is configured as the left-side app in the sync setup.

This means you’ll be mapping fields from the Wix (left side) to the corresponding fields in the other app (right side).

  1. Select the tables you want to sync between the two apps.

Step 5: Choose Which Data to Sync

For each sync, you'll need to select whether to sync existing records, future changes, or both.

Step 6: Configure Field Mapping

  1. On the Field Mapping screen, drag and drop fields from the right panel into the mapped fields column to create mappings.

  2. To delete a mapping, click the X button next to the field.
  3. Select the sync direction at the field level using the arrow buttons.One-Way Sync: Data flows from one app to the other.Two-Way Sync: Data flows bidirectionally between both apps.
  4. Once your mappings are finalized, click "Continue.

Step 7: Sync Existing Data Configuration

Select the sync direction for your existing data.

Step 8: Review Sync Preview

  1. Preview the sync setup to ensure everything is configured correctly.
  2. If all looks good, click "Start Sync."
  3. Byteline will:
    • Perform an initial sync of your existing data.
    • Keep the sync running automatically, ensuring your Wix data stays up to date.

You can monitor sync progress, view logs, or make changes anytime from the Syncs page. If you need to pause or edit the sync, simply open it from your dashboard.

✅ That’s it! Your Wix sync is now live.

Wix CMS Support Details

Handling Wix CMS Reference and Multi-reference fields

Byteline makes it easy to work with Wix CMS reference and multi-reference fields by allowing you to map them using human-readable text values. These values must exactly match the primary field of the referenced collection. The primary field is the one displayed in the Wix CMS dashboard for each item.

You can view which field is set as primary by clicking the Manage Fields button.

Clicking Manage Fields opens the following screen

If needed, you can change the primary field by clicking the three-dot menu next to a text field and selecting Make Primary.

Rich Content Supported Elements

We support syncing all major elements from Wix’s rich content field, including:

  • Text & Formatting: Headings, paragraphs, bold, italic, underline, strikethrough, colors, alignment, block quotes
  • Lists: Bullet lists, numbered lists
  • Media: Images, videos, audios, gallery
  • Links & Code: Hyperlinks, code blocks
  • Layout & Advanced: Tables, dividers, embedded content
Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive document will walk you through the step-by-step configuration process for Google Sheet data sync and address specific use cases tailored to Google Sheet.

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers usages of data sync features valid for all integrations.

Prerequisites

  1. The spreadsheet must have a header row with a label for each column.
  2. Install the "Byteline - Data Sync" Google Sheets add-on on your spreadsheet by following the instructions outlined in the Step-by-Step Guide to Install "Byteline - Data Sync" Google Sheets Add-On.

    Byteline no longer uses the Byteline Last Modified Time (DO NOT CHANGE) column. If this column exists in your spreadsheet, you can safely ignore its values.

  3. Before configuring the Google Sheets data sync, ensure your spreadsheet adheres to the format below. The first four columns provided are merely examples; naturally, you will have your own column names.

Configuring Google Sheet Data Sync

  1. Go to the Byteline Console.
  2. Click on the Create Sync button.
  3. In the "Select your first service" section, select Google Sheets.
  4. Click Sign in with Google if you are not already signed in.
  5. On the next page, click Sign in and complete the Google authorization steps.

  6. Click the Give permission button and select the spreadsheets you want to use for the data sync.

  7. The Byteline Google Sheets connection is now complete, and the data sync configuration page will update as shown below.

  8. Configure the second app you want to sync data to/from, and click Save & Proceed.
  9. Follow the steps explained in the Data Sync - Getting Started document to configure table and field mapping.

Real-time Updates

Byteline provides real-time updates from Google Sheets. Any time you create a row, update cells, or delete a row, the changes are instantly synchronized.

Note: Real-time updates are only available for manual changes to your Google Sheets. If a formula-based column updates due to a manual change, that update will also be captured immediately.

Reauthorizing your Spreadsheet for Real-time Updates

If you have been using our Google Sheets add-on before real-time updates were supported, follow these steps to reauthorize the Byteline add-on:

  1. Open your Google spreadsheet, and click on Extensions -> Byteline - Data Sync & Automation -> Open
  2. Click OK on the below dialog presented by Google.

  3. Complete the Google authorization steps

After completing these steps, any manual changes to your Google Spreadsheet will be instantly available in a live sync.

Synchronizing Non-Manual Changes

Byteline fully supports rows that are created, updated, or deleted through non-manual methods such as automations, form submissions, or other connected apps. No additional setup is required to handle this data. However, please note that these changes are not processed in real time—they will be picked up within 5 to 15 minutes, depending on your subscription plan.

Do not delete the header row of your Google Sheets, as it is essential for mapping and syncing data.

By following these guidelines, you can maintain accurate data synchronization with Byteline and ensure that your Google Sheets data is up-to-date with non-manual changes.

Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive document will walk you through the step-by-step configuration process for QuickBooks data sync and address its specific use cases.

Supported Objects

Byteline supports syncing the following data objects from QuickBooks:

  • Customers

More object types will be supported in the future.

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers usages of data sync features valid for all integrations.

Installing app

  1. Go to QuickBooks Marketplace
  2. Search for "Byteline Sync"
  3. Select the app and click on the "Get app now" button.

  4. After installing the app, refer to the next section on configuring a data sync.

Configuring QuickBooks Data Sync

Step 1: Start the Sync Setup

  1. Log in to your Byteline account and navigate to the My Syncs page.
  2. Click on the "Create Sync" button to begin the configuration.

Step 2: Select QuickBooks as your first app

  1. Choose QuickBooks as the first app to sync. Alternatively, you can select another app first and then pick QuickBooks as the second app.

  2. Click on "Connect to QuickBooks" button to connect your QuickBooks account to Byteline.

Step 3: Choose QuickBooks Data Type

  1. Select the QuickBooks data you wish to sync. Byteline supports the following:
  • Customers

Step 4: Connect the Second App

  1. Select the second app for syncing and log in to authorize the connection.
  2. Once connected, click "Continue" to move to the table mapping screen.

Step 5: Map Tables Between QuickBooks and the Other App

  1. Select the tables to sync between both apps. For all QuickBooks objects, you’ll see a single table available in the dropdown menu.

  2. Select the tables you want to sync between the two apps.

Step 6 - Select Which Data to Sync

Step 7: Configure Field Mapping

  1. On the Field Mapping screen, drag and drop fields from the right panel into the mapped fields column to create mappings.

  2. To delete a mapping, click the X button next to the field.
  3. Select the sync direction at the field level using the arrow buttons.1-Way Sync: Data flows from one app to the other.2-Way Sync: Data flows bidirectionally between both apps.
  4. Once your mappings are finalized, click "Continue."

Step 7: Sync Existing Data Configuration

  1. Select the sync direction for your existing data:

Step 8: Review Sync Preview

  1. Preview the sync setup to ensure everything is configured correctly.
  2. If all looks good, click "Start Sync."
  3. Byteline will sync your existing data and make the sync live.

Step 9: Automatic Record Syncing

Once the sync is live, any changes made to records in either app will automatically sync to the other app in real time.

Why Use Byteline for QuickBooks Data Sync?

Byteline simplifies the process of syncing data between QuickBooks and other apps, ensuring:

  • Real-time data synchronization.
  • Easy-to-use field mapping and sync direction configuration.
Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive document will walk you through the step-by-step configuration process for PostgreSQL data sync and address specific use cases tailored to PostgreSQL .

Pre-requisites

Your PostgreSQL tables must have a primary key column. If you don't have it, please refer to the section below on adding it.

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers the usage of data sync features valid for all integrations.

Configuring PostgreSQL Data Sync

Step 1: Start the Sync Setup

  1. Log in to your Byteline account and navigate to the My Syncs page.
  2. Click on the "Create Sync" button to begin the configuration.

Step 2: Select PostgreSQL as Your First App

  1. Choose PostgreSQL as the first app to sync.Alternatively, you can select another app first and then pick PostgreSQL as the second app.

  2. Click on the "Sign In" button under PostgreSQL to connect it to Byteline.
  3. Now select the PostgreSQL schema that you want to use.

Step 3: Connect the Second App

  1. Select the second app for syncing and log in to authorize the connection.
  2. Once connected, click "Continue" to move to the table mapping screen.

Step 4: Map Tables Between PostgreSQL and the Other App

  1. Select the tables you want to sync between the two apps.

Step 5: Select Which Data to Sync

Step 6: Configure Field Mapping

  1. On the Field Mapping screen, drag and drop fields from the right panel into the mapped fields column to create mappings.

  2. To delete a mapping, click the X button next to the field.
  3. Select the sync direction at the field level using the arrow buttons.One-Way Sync: Data flows from one app to the other.Two-Way Sync: Data flows bidirectionally between both apps.
  4. Once your mappings are finalized, click "Continue."

Step 7: Sync Existing Data Configuration

Select the sync direction for your existing data:

Step 8: Review Sync Preview

  1. Preview the sync setup to ensure everything is configured correctly.
  2. If all looks good, click "Start Sync."
  3. Byteline will sync your existing data and make the sync live.

Configuring a Primary Key for Your PostgreSQL Table

A primary key is required on a table for it to work with data sync. If your PostgreSQL table doesn’t already have a primary key, you can add one using either of the methods below.

Option 1: Add an Auto-Generated Primary Key (Recommended)

Use this method when your table doesn’t already have a suitable column for a primary key. Note: You have to complete steps 1 & 2.

Step 1: Add an identity column

ALTER TABLE blogs
ADD COLUMN id INT GENERATED ALWAYS AS IDENTITY;

Step 2: Add the primary key constraint

After ensuring that the ID column has been created and is unique:

ALTER TABLE blogs ADD PRIMARY KEY (id);

Option 2: Use an Existing Column as Primary Key

Use this method if you already have a column (like title, email, or user_id) that contains unique values.

⚠️ Important: The column you select must have unique and non-null values.

ALTER TABLE blogs ADD PRIMARY KEY (title);

Whitelisting IP Address for PostgreSQL Connections

To establish a secure and successful connection between your database and our data sync system, some hosting providers or firewall configurations may require you to whitelist our static IP address.

If your PostgreSQL database is hosted in a data center or cloud environment with IP restrictions, please ensure that the following IP address is allowed to connect:

➡️ IP to Whitelist: 3.21.72.72

Why is this needed?

Our data sync platform initiates the connection to your PostgreSQL database from the above IP. If your server blocks unknown IPs, whitelisting this address ensures that our sync operations can reach your database without interruption.

Ensure that the IP is whitelisted for port 5432 (the default PostgreSQL port), unless your database uses a different port.

⚠️ Note: If you are unsure how to whitelist an IP, please consult your database or hosting provider’s documentation or support team.

Once the IP is whitelisted, proceed with configuring the PostgreSQL connector in your data sync setup.

Syncing Data from localhost Using Ngrok

Usually, your database wouldn't be on the local machine. But if it is, and you want to sync data to or from it using Byteline, Ngrok can help expose your local database to the internet securely.

Steps to Access a Local Database Using Ngrok

1. Install Ngrok

Download and install Ngrok from https://ngrok.com/download. Follow the installation instructions provided for your operating system.

2. Expose Your Local Database Using Ngrok

Ngrok can expose a TCP connection for your local database. Use the following command to expose your database:

ngrok tcp <port>

Replace <port> with the port your database is running on (e.g., 5432 ).

Example for a PostgreSQL database running on port 5432:

ngrok tcp 5432

Ngrok will generate a public TCP address (e.g., 0.tcp.ngrok.io:12345) that tunnels to your local database.

3. Update Database Configuration in Byteline

In the Byteline data sync configuration, use the Ngrok TCP address as the database host. For example:

Host: 0.tcp.ngrok.io

Port: 12345

Username: Your database username

Password: Your database password

Database Name: The name of your database

4. Test the Connection

Use the "Test Connection" feature in Byteline to ensure the platform can connect to your local database through the Ngrok TCP tunnel.

5. Run the Sync

After successfully testing the connection, initiate the data sync as you normally would. Byteline will access your local database through the Ngrok tunnel.

Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive document will walk you through the step-by-step configuration process for MySQL data sync and address specific use cases tailored to MySQL .

Pre-requisites

Your MySQL tables must have a primary key column. If you don't have it, please refer to the section Configuring a Primary Key for Your MySQL Table for adding it.

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers the usage of data sync features valid for all integrations.

Configuring MySQL Data Sync

Step 1: Start the Sync Setup

  1. Log in to your Byteline account and navigate to the My Syncs page.
  2. Click on the "Create Sync" button to begin the configuration.

Step 2: Select MySQL as Your First App

  1. Choose MySQL as the first app to sync.Alternatively, you can select another app first and then pick MySQL as the second app.

  2. Click on the "Sign In" button under MySQL to connect it to Byteline.
  3. Now select the MySQL schema that you want to use.

Step 3: Connect the Second App

  1. Select the second app for syncing and log in to authorize the connection.
  2. Once connected, click "Continue" to move to the table mapping screen.

Step 4: Map Tables Between MySQL and the Other App

  1. Select the tables you want to sync between the two apps.

Select Which Data to Sync

Step 6: Configure Field Mapping

  1. On the Field Mapping screen, drag and drop fields from the right panel into the mapped fields column to create mappings.

  2. To delete a mapping, click the X button next to the field.
  3. Select the sync direction at the field level using the arrow buttons.One-Way Sync: Data flows from one app to the other.Two-Way Sync: Data flows bidirectionally between both apps.
  4. Once your mappings are finalized, click "Continue."

Step 7: Sync Existing Data Configuration

Select the sync direction for your existing data:

Step 8: Review Sync Preview

  1. Preview the sync setup to ensure everything is configured correctly.
  2. If all looks good, click "Start Sync."
  3. Byteline will sync your existing data and make the sync live.

Configuring a Primary Key for Your MySQL Table

A primary key is required on a table for it to work with data sync. If your MySQL table doesn’t already have a primary key, you can add one using either of the methods below.

Option 1: Add an Auto-Increment Primary Key (Recommended)

Use this method when your table doesn’t already have a suitable column for a primary key. This adds a new column that automatically generates unique IDs and sets it as the primary key.

ALTER TABLE blogs ADD COLUMN id INT AUTO_INCREMENT PRIMARY KEY;

This adds a new id column that:

  • Auto-increments with each new row
  • Acts as the primary key

Option 2: Use an Existing Column as Primary Key

Use this method if you already have a column (like title, email, or user_id) that contains unique and non-null values.

⚠️ Important: The column you choose must not contain duplicate or NULL values.

ALTER TABLE blogs ADD PRIMARY KEY (title);

Whitelisting IP Address for MySQL Connections

To establish a secure and successful connection between your database and our data sync system, some hosting providers or firewall configurations may require you to whitelist our static IP address.

If your MySQL database is hosted in a data center or cloud environment with IP restrictions, please ensure that the following IP address is allowed to connect:

➡️ IP to Whitelist: 3.21.72.72

Why is this needed?

Our data sync platform initiates the connection to your MySQL database from the above IP. If your server blocks unknown IPs, whitelisting this address ensures that our sync operations can reach your database without interruption.

Ensure that the IP is whitelisted for port 3306 (the default MySQL port), unless your database uses a different port.

⚠️ Note: If you are unsure how to whitelist an IP, please consult your database or hosting provider’s documentation or support team.

Once the IP is whitelisted, proceed with configuring the MySQL connector in your data sync setup.

Syncing Data from localhost Using Ngrok

Usually, your database wouldn't be on the local machine. But if it is, and you want to sync data to or from it using Byteline, Ngrok can help expose your local database to the internet securely.

Steps to Access a Local Database Using Ngrok

1. Install Ngrok

Download and install Ngrok from https://ngrok.com/download. Follow the installation instructions provided for your operating system.

2. Expose Your Local Database Using Ngrok

Ngrok can expose a TCP connection for your local database. Use the following command to expose your database:

ngrok tcp <port>

Replace <port> with the port your database is running on (e.g., 3306).

Example for a MySQL database running on port 3306:

ngrok tcp 3306

Ngrok will generate a public TCP address (e.g., 0.tcp.ngrok.io:12345) that tunnels to your local database.

3. Update Database Configuration in Byteline

In the Byteline data sync configuration, use the Ngrok TCP address as the database host. For example:

Host: 0.tcp.ngrok.io

Port: 12345

Username: Your database username

Password: Your database password

Database Name: The name of your database

4. Test the Connection

Use the "Test Connection" feature in Byteline to ensure the platform can connect to your local database through the Ngrok TCP tunnel.

5. Run the Sync

After successfully testing the connection, initiate the data sync as you normally would. Byteline will access your local database through the Ngrok tunnel.

Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive document will walk you through the step-by-step configuration process for HubSpot data sync and address specific use cases tailored to HubSpot .

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers usages of data sync features valid for all integrations.

Installing app

  1. Go to HubSpot Marketplace
  2. Search for "Byteline Sync"
  3. Select the app and click on the Install app button.

  4. After installing the app, refer to the next section on configuring a data sync.

Configuring HubSpot Data Sync

Step 1: Start the Sync Setup

  1. Log in to your Byteline account and navigate to the My Syncs page.
  2. Click on the "Create Sync" button to begin the configuration.

Step 2: Select HubSpot as Your First App

  1. Choose HubSpot as the first app to sync.
    • Alternatively, you can select another app first and then pick HubSpot as the second app.

  2. Click on "Sign In" under HubSpot to connect your HubSpot account to Byteline.

Step 3: Choose HubSpot Object Type

  1. Select the HubSpot object you wish to sync. Byteline supports the following HubSpot objects:
    • Contacts
    • Companies
    • Deals
    • Custom Objects.

Step 4: Connect the Second App

  1. Select the second app for syncing and log in to authorize the connection.
  2. Once connected, click "Continue" to move to the table mapping screen.

Step 5: Map Tables Between HubSpot and the Other App

  1. Select the tables to sync between both apps. For all HubSpot objects (except Custom Objects), you’ll see a single table available in the dropdown menu.

  2. Select the tables you want to sync between the two apps.

Step 6: Configure Field Mapping

  1. On the Field Mapping screen, drag and drop fields from the right panel into the mapped fields column to create mappings.

  2. To delete a mapping, click the X button next to the field.
  3. Select the sync direction at the field level using the arrow buttons.One-Way Sync: Data flows from one app to the other.Two-Way Sync: Data flows bidirectionally between both apps.
  4. Once your mappings are finalized, click "Continue."

Step 7: Sync Existing Data Configuration

  1. Select the sync direction for your existing data:

Step 8: Review Sync Preview

  1. Preview the sync setup to ensure everything is configured correctly.
  2. If all looks good, click "Start Sync."
  3. Byteline will sync your existing data and make the sync live.

Step 9: Automatic Record Syncing

Once the sync is live, any changes made to records in either app will automatically sync to the other app in real time.

Why Use Byteline for HubSpot Data Sync?

Byteline simplifies the process of syncing data between HubSpot and other apps, ensuring:

  • Real-time data synchronization.
  • Support for multiple HubSpot object types, including Contacts, Companies, Deals, and Custom Objects.
  • Easy-to-use field mapping and sync direction configuration.
Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive document will walk you through the step-by-step configuration process for Campaign Monitor data sync and address its specific use cases.

Supported Objects

Byteline supports syncing the following data objects from QuickBooks:

  • Subscribers

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers the usage of data sync features valid for all integrations.

Configuring Campaign Monitor Data Sync

Step 1: Start the Sync Setup

  1. Log in to your Byteline account and navigate to the My Syncs page.
  2. Click on the "Create Sync" button to begin the configuration.

Step 2: Select Campaign Monitor as Your First App

  1. Choose Campaign Monitor as the first app to sync.Alternatively, you can select another app first and then pick Campaign Monitor as the second app.
  2. Click on the "Sign In" button under Campaign Monitor to connect it to Byteline.
  3. Now select the Subscriber for the data type to sync.
  4. Select the client for which the data needs to be synced.

Step 3: Connect the Second App

  1. Select the second app for syncing and log in to authorize the connection.
  2. Once connected, click "Continue" to move to the table mapping screen.

Step 4: Map Tables Between Campaign Monitor and the Other App

  1. Select the tables you want to sync between the two apps.

Step 5: Select Which Data to Sync

Step 6: Configure Field Mapping

  1. On the Field Mapping screen, drag and drop fields from the right panel into the mapped fields column to create mappings.

  2. To delete a mapping, click the X button next to the field.
  3. Select the sync direction at the field level using the arrow buttons.One-Way Sync: Data flows from one app to the other.Two-Way Sync: Data flows bidirectionally between both apps.
  4. Once your mappings are finalized, click "Continue.

Step 7: Sync Existing Data Configuration

Select the sync direction for your existing data:

Step 8: Review Sync Preview

  1. Preview the sync setup to ensure everything is configured correctly.
  2. If all looks good, click "Start Sync."
  3. Byteline will sync your existing data and make the sync live.

Updated
November 13, 2026
Excerpt is generated from the doc content.

Updating Sync after changing the app field types

Sometimes you need to change the column field type in your app, e.g., Airtable. This action will cause the field types in your existing sync to differ from those in the app. Please follow the below steps to refresh the sync field types.

  1. Go to sync and click Edit.
  2. If the sync is live, stop the sync.
  3. Navigate to the "Map fields" screen, the third screen.
  4. Click on the Refresh button.

  5. Now Save the sync.
  6. Hit "Start Sync" to turn the sync back to live.

Your sync will now have up-to-date field types.

Refresh Poller-driven Apps

For Cloud-based applications like Notion, which rely on polling mechanisms for tracking data changes, there inevitably exists a lag between modifications within the app and their visibility to Byteline. This causes a time delay for a user to test our changes. So Byteline provides a way to force the "Refresh" for such apps.

To trigger this refresh, simply utilize the "Refresh" link conveniently located next to the table, as illustrated in the accompanying screenshot. Byteline promptly initiates a check for any recent changes, ensuring immediate synchronization.

Updated
November 13, 2026
Excerpt is generated from the doc content.

This comprehensive document will walk you through the step-by-step configuration process for Fibery data sync and address specific use cases tailored to Fibery.

Standard Data Sync functionality

Please refer to Data Sync - Getting Started for the standard data sync functionality. The getting started document covers usages of data sync features valid for all integrations.

Requirements

  1. You must be an admin on the account to set up a sync.
    1. Click on the hostname and navigate to Settings → Users.

    2. Confirm that you have the Admin role

Installing app

  1. Go to Byteline Console.
  2. Select the first app as Fibery and Sign In to create the connection.
  3. Refer to the next section on configuring a data sync.

Configuring Fibery Data Sync

Step 1: Start the Sync Setup

  1. Log in to your Byteline account and navigate to the My Syncs page.
  2. Click on the "Create Sync" button to begin the configuration.

Step 2: Select Fibery as Your First App

  1. Choose Fibery as the first app to sync.
    • Alternatively, you can select another app first and then pick Fibery as the second app.

  2. Click on "Sign In" under Fibery to connect your Fibery account to Byteline.

Step 3: Choose Fibery Database

  1. Select the Fibery database you wish to sync.

Step 4: Connect the Second App

  1. Select the second app for syncing and log in to authorize the connection.
  2. Once connected, click "Continue" to move to the table mapping screen.

Step 5: Map Tables Between Fibery and the Other App

  1. Select the tables to sync between both apps.
  2. Select the tables you want to sync between the two apps.

Step 6: Configure Field Mapping

  1. On the Field Mapping screen, drag and drop fields from the right panel into the mapped fields column to create mappings.

  2. To delete a mapping, click the X button next to the field.
  3. Select the sync direction at the field level using the arrow buttons.One-Way Sync: Data flows from one app to the other.Two-Way Sync: Data flows bidirectionally between both apps.
  4. Once your mappings are finalized, click "Continue."

Step 7: Sync Existing Data Configuration

  1. Select the sync direction for your existing data:

Step 8: Review Sync Preview

  1. Preview the sync setup to ensure everything is configured correctly.
  2. If all looks good, click "Start Sync."
  3. Byteline will sync your existing data and make the sync live.

Step 9: Automatic Record Syncing

Once the sync is live, any changes made to records in either app will automatically sync to the other app in real time.

Updated
November 13, 2026