Developer

GitHub Integration

Zynk's GitHub integration commits files from your workflows into a GitHub repository. Price lists, product catalogues, configuration files or reports exported from Sage, Shopify and other systems are created or updated with a commit message, giving technical teams a version history and one place to review what changed between runs and when.

Available for

Workflow

Capabilities may differ depending on the product.

See what you can do Book a call →

Benefits

Why businesses connect GitHub

A history of every change

Each file Zynk writes to GitHub arrives as a commit with its own message. Compare any two versions of a price list or catalogue to see exactly what changed between workflow runs, and on which day.

Create, update or upsert

Choose whether each file must be new, must already exist, or should be created or replaced as needed. Upsert is the default, so a nightly export simply replaces last night's copy with a fresh commit.

Files land where you want them

Commit to any repository the connected account can update, including one owned by another user or organisation. A separate repository path lets the local file name and its location on GitHub differ.

Business data where developers look

Product data, prices and settings arrive in the repository your developers and build tools already use, so a site, app or script can read the latest version without asking for access to the accounts or the shop admin.

Successes and failures on record

The task writes committed files to a success file and anything GitHub rejects to a fail file along with the error message, so a failed commit is visible and can be retried rather than quietly missed.

Capabilities

What you can do with GitHub

Every task the Zynk GitHub connector can run, grouped by the direction data moves.

Import into GitHub

Data Zynk writes into GitHub

1 task

Repository files → into GitHub

Need something that isn't listed?

Most GitHub projects include at least one custom step. Our team builds it for you.

Talk to us

The problem

Why integrate GitHub?

Exports from business systems tend to overwrite each other. Last week's price list disappears once this week's arrives, and nobody can say which product or setting changed. Teams that already work in GitHub want that data under version control, but copying files in and committing them by hand rarely survives a busy week.

Without integration

Each export overwrites the last, so earlier versions are lost
No record of when a price or setting changed
Developers chasing finance or ecommerce teams for the latest file
Files committed by hand, when somebody remembers

With Zynk

Every run is committed, so earlier versions stay in the history
Commit messages and timestamps show what changed on each run
The latest export is always in the repository developers already use
Commits happen automatically as part of a scheduled workflow

How it works

How the GitHub integration works

Step 1: Connect your GitHub account
Add a GitHub connection in Zynk with your username and a personal access token. GitHub requires the token to have write access to repository contents before files can be created or updated.
Step 2: Produce the files
Earlier tasks export the data, for example products from Shopify or price bands from Sage 200, and convert it into the format you want to keep, such as JSON, CSV or XML.
Step 3: Describe the commits
An XML input, usually built by an XSLT transform, names the repository, each file, the operation to use and its commit message. File contents can come from disk or as a base64 string.
Step 4: Put it on a schedule
Run the workflow on whatever timetable suits, such as nightly after the main export. Every successful run leaves a commit that anyone with access to the repository can review.

Integrations

What can you connect to GitHub?

CSV

Example use cases for GitHub integration

GitHub and Shopify

Export products from Shopify and commit them to a repository each night, so the history shows when titles, prices or variants changed and what they were before.

Products

View the Shopify integration →

GitHub and Sage 200

Commit Sage 200 price bands to GitHub after each export, giving a dated record of pricing changes that the team can compare line by line.

Price bands

View the Sage 200 integration →

GitHub and Sage 50 UK

Keep a versioned copy of Sage 50 price lists in a repository, ready for a website build or script to read without needing access to the accounts.

Price lists

View the Sage 50 UK integration →

GitHub and JSON

Convert workflow output with XML To JSON before committing, so the files in the repository are easy for developers and their tools to read.

JSON files

View the JSON integration →

Find your integration →

GitHub integration FAQs

What does the Zynk GitHub integration do?

It commits files into GitHub repositories as part of a Zynk workflow. You supply the files, the repository and a commit message, and Zynk creates or updates each file, logging results to success and fail files. It does not deploy code or manage issues and pull requests.

Can Zynk read files from a GitHub repository?

The GitHub connector's task, Import Repository Files, writes files into a repository rather than reading them out. If a workflow needs to fetch a file from GitHub, the HTTP connector can call GitHub's REST API with the right headers instead.

What GitHub permissions does Zynk need?

The connection uses your GitHub username and a personal access token. A classic token needs the repo scope to create or update files, and a fine-grained token needs write access to Contents on each repository Zynk will update.

Does every update create a commit?

Yes. Each file Zynk creates or updates through GitHub's API is recorded as a commit carrying the message you supply. That builds a full history in the repository, and earlier versions can be viewed or compared in GitHub in the usual way.

Can I commit a file that is not saved on the Zynk server?

Yes. As well as reading a local file path, the task accepts file contents as a base64 encoded string in its input. That suits content produced by an earlier task that you would rather not write to disk before it is committed.

Which business systems can feed a GitHub repository?

Any system Zynk can export from. Examples include product data from Shopify or Magento, price lists from Sage 50 or Sage 200 and records from Salesforce, converted to JSON or CSV and committed so developers and their tools can work with them.

Can Zynk commit to a repository owned by my organisation?

Yes. If the repository belongs to an organisation or another user rather than the account in the connection, add the owner's name to the task input. The token still needs write access to that repository's contents for the commit to succeed.

See what Zynk can automate for your GitHub setup

Book a 20-minute call. We'll review your systems, flag the quick wins and outline a practical route to going live.

Book a call See pricing →