2i2c-org/data-sync keeps data in sync from one system to another (“sync A to B”).
It runs scheduled GitHub Actions that read from each source and write changes into the destination.
What runs today¶
Here are a few examples, see 2i2c-org/data-sync for the current list.
Label a GitHub issue with a sync label: a task is created in our Asana activity log that mirrors fields like
GitHub Hours(plus title and status) from GitHub -> Asana. The list of sync labels lives in the data-sync repository.Add an ‘Asana Engagement URL’ to a HubSpot Deal: the matching Asana engagement project will now be updated using HubSpot metadata.
Add a HubSpot Deal URL to a GitHub
Sales Issue: the issue URL will be added to the HubSpot deal, and HubSpot data will now be synced back to the issue body.
See the Create a GitHub Sales Issue to a HubSpot Deal? section in the HubSpot and CRM guide document for the workflow details.
Seeing what changed¶
Syncs append to a shared audit-log spreadsheet when something is worth flagging (e.g., a skipped record, or over-writing a URL in HubSpot). It’s a place to spot problems, not a complete record of everything that synced.
See the repository documentation for sync details and how to add a new one.
When a sync fails¶
When a scheduled sync fails, a bot posts a message in the #operations Slack channel with a link to the failed run.
This covers the syncs in 2i2c-org/data-sync and the daily MAU update in 2i2c-org/data.
The bot posts through a Slack webhook, which is a private URL that can send messages to #operations.
The URL is stored in the SLACK_OPERATIONS_WEBHOOK_URL organization secret, and only the repositories listed on that secret can use it.
If another job’s failures would be useful in #operations, add an alert for it:
On the secret’s settings page, give the job’s repository access to the secret.
Copy the “Alert Slack on failure” step from one of the data-sync workflows to the end of the job.