Overview Installation Guide User Guide Terms of Service Privacy Policy
SyncBig / Documentation

User Guide

SyncBig automates the flow of your BigCommerce store data into Google Sheets, Asana, and Slack. Once you create a sync job, it runs automatically in the background on your chosen schedule.

Overview

SyncBig automates the flow of your BigCommerce store data into Google Sheets, Asana, and Slack. Once you create a sync job, it runs automatically in the background on your chosen schedule. You can manage all your jobs and review sync history from the App's dashboard.

The Dashboard

When you open SyncBig, you land on the Dashboard. It shows:

StatWhat It Shows
Total JobsTotal number of sync jobs created for your store
Active JobsJobs currently enabled and scheduled to run
Total Syncs TodayAll sync runs completed since midnight UTC
Successful TodaySyncs that completed without error today
Failed TodaySyncs that encountered an error today

The Recent Active Sync Jobs table shows your latest 5 active jobs with their last run time and next scheduled run. Click any row to jump to that job's sync history. Click any stat card to jump to a filtered view of your jobs or logs.

Creating a Sync Job

Click New Sync Job from the dashboard or the Jobs page. The job form has five steps:

Step 1 — Data Type

Choose what BigCommerce data to sync:

  • Orders — order records including status, totals, customer info
  • Products — product catalogue records including SKU, price, inventory
  • Customers — customer account records including name and email

Step 2 — Destination

Choose where to send the data:

Google Sheets

  • Paste the full URL of your Google Sheet (e.g. https://docs.google.com/spreadsheets/d/…/edit)
  • The sheet must be set to Anyone with the link → Editor in Google Sheets sharing settings
  • Optionally specify a sheet tab name (defaults to Sheet1)
  • The App validates your sheet URL and access before you can proceed

Asana

  • Click Connect Asana to authorize via OAuth (one-time setup per store)
  • Select a Workspace then a Project from the dropdowns
  • Synced records will be created as Asana tasks, with your selected fields mapped to custom fields on the project

Slack

  • Click Connect Slack to authorize via OAuth (one-time setup per store)
  • Select a channel from the dropdown
  • Choose a sync mode — Summary Alert sends a single message summarizing all new records from the sync run

Step 3 — Condition

Select the data condition you want included in each sync run. The available conditions vary by data type. At least one condition must be selected.

Step 4 — Fields

Select the data fields you want included in each sync run. The available fields vary by data type. At least one field must be selected.

Step 5 — Schedule

Give the job a name and set its schedule:

FrequencyTime InputBehaviour
HourlyMinute of each hour (e.g. :15)Runs at XX:15 every hour
Every 6 HoursStarting at (e.g. 06:30)Runs at 06:30, 12:30, 18:30, 00:30 UTC
Every 12 HoursStarting at (e.g. 08:00)Runs at 08:00, 20:00 UTC
DailyStarting at (e.g. 09:00)Runs at 09:00 UTC each day
WeeklyStarting at + day of weekRuns at the specified time on the chosen weekday
MonthlyStarting at + day of monthRuns at the specified time on the chosen date (or last day)
OnceRuns one time only, then auto-pauses
All times are user timezone based.

Also choose Sync Data From:

  • From now — only sync records created or updated after this job is created (best for ongoing operational feeds)
  • From the beginning — full historical sync on first run (best for reporting and analysis)
  • Custom date — sync records from a specific date and time onwards

Click Create Job to save. The job is created with status Active and will run at its next scheduled time.

Managing Jobs

Navigate to Sync Jobs from the menu to see all your sync jobs.

Editing a Job

Click a job's name to open it, then click Edit. You can change the job name, schedule, and sync start point. Changing the schedule recalculates the next run time immediately.

Pausing a Job

Click Pause on any active job. The job stops running but retains all its settings. Click Resume to re-enable it — the next run time is recalculated from the current moment.

Deleting a Job

Click Delete and confirm. The job and all its sync history logs are permanently removed.

Sync History

Navigate to Sync History from the sidebar to see a log of all sync runs.

Filter options:

  • By Job — view runs for a specific job only
  • By Status — Success, Failed, or Running
  • By Date Range — Last 24 hours, Last 7 days, Last 30 days

Log columns:

  • Job Name — which job triggered the run
  • Data Type — Orders, Products, or Customers
  • Started — date and time the run began
  • Status — Success, Failed, or Running
  • Rows Synced — number of records written to the destination

Reconnecting Asana or Slack

If your Asana or Slack connection expires or is revoked, you can reconnect by editing any job that uses that destination and clicking the Connect button again to re-authorize via OAuth.

Uninstalling

To uninstall SyncBig, go to Apps in your BigCommerce control panel, find SyncBig, and click Uninstall. All your jobs, sync history, and OAuth tokens are permanently deleted from our systems.

Frequently Asked Questions

How quickly after a sync schedule fires will my data arrive at the destination?

SyncBig checks for due jobs every 5 minutes, so a scheduled job may run up to 5 minutes after its configured time.

Will my Google Sheet be overwritten on each sync?

SyncBig appends new rows to your sheet on each run by default. You can set Sync Mode to “Replace all data” to overwrite your sheet on every sync.

What happens if a sync fails?

The failure is logged in Sync History with an error message. The job remains Active and will attempt to run again at its next scheduled time.

Can I run a job immediately without waiting for the schedule?

Yes. Create a job with the Once schedule type — it will be picked up on the next cron tick (within 5 minutes).

Does SyncBig support multiple stores?

Yes. Each BigCommerce store that installs the App gets its own isolated set of jobs, logs, and OAuth connections.

My Asana tasks are duplicated after re-running a job. Why?

SyncBig employs incremental syncing, automatically fetching only those records modified since the last successful run. To prevent duplicates, the system automatically updates a custom date field after each sync, which then serves as the "start date" for the subsequent cycle. If you changed the Sync Data From setting to From the beginning on an edit, the next run will re-sync all historical records.

Still have questions? admin@aizlabs.com