Keep Lightspeed and GitHub updated automatically.
Today you open your shop’s admin, look at which orders came in and carry them over. This connector fixes that, and we build it on request: what happens in Lightspeed lands in GitHub by itself, in the shape GitHub expects. Tell us what you need and we agree exactly what should travel.
What this connector takes off your hands
-
Today you open your shop’s admin, look at which orders came in and carry them over.
-
Today you create the task or the row yourself, or you just remember it and that fails eventually.
What Lightspeed to GitHub saves you
- Turn every new Lightspeed order into a GitHub task automatically.
- Turn every refund in Lightspeed into a GitHub task automatically.
- Turn every new Lightspeed customer into a GitHub task automatically.
- Turn every stock change in Lightspeed into a GitHub task automatically.
What travels across the link
Everything this connector moves between Lightspeed and GitHub, and how often.
-
Tasks
to GitHub automaticallyThis lands in GitHub as a task in the list or project you choose, so follow-up does not depend on someone remembering.
-
Rows
to GitHub automaticallyThis arrives in GitHub as a new row, so your overview stays complete without you retyping anything.
What each side expects
Lightspeed and GitHub do not describe the world the same way. This is what has to line up.
GitHub
A task list or table wants to know where something belongs, and only stays usable with a fixed layout.
Setting it up
- 01
Request the connector
Let us know you want to link Lightspeed to GitHub. We get in touch within 24 hours with a timeline.
- 02
We agree what should travel
Together we settle what should travel out of Lightspeed. A task list or table wants to know where something belongs, and only stays usable with a fixed layout.
- 03
We build and test
You see the connector run on a few test records before anything becomes final.
What you need
- A store you administer, with API access from its admin.
- An account with edit rights, and the list or project it should land in.
Where it runs
Inside your Shopify admin, as an app. You sign in through Shopify, no separate account.
We build this connector on request. Tell us what you need and we reply within 24 hours.
Common questions
Can you connect Lightspeed to GitHub?
Yes. Schakel connects through the official APIs of Lightspeed and GitHub, so you install nothing on your own server and nothing travels outside those two parties.
Which GitHub project or list do the tasks land in?
The project or list you choose. That keeps everything in one place rather than scattered, and follow-up does not depend on someone remembering.
Can I decide what goes into the GitHub task or row?
Yes. When setting it up you pick which details from Lightspeed come along, so a task or row in GitHub has just enough context.
What happens on a refund or partial cancellation in Lightspeed?
It comes across, so GitHub matches what was actually settled and you correct nothing by hand.
What does connecting Lightspeed and GitHub cost?
You start free and only pay once the connector is really running. After that the same tiers apply as for any other connector, based on how much runs through it each month.
How often does Lightspeed sync with GitHub?
That depends on your tier: hourly on the free tier up to real time on the unlimited tier. You can always start a sync yourself as well.
What if Lightspeed or GitHub is briefly unavailable?
Nothing gets lost. Schakel retries later and the log shows exactly what happened, so at most you notice something coming through a little later.
How do I connect Lightspeed to GitHub?
You give Schakel access to Lightspeed and GitHub once and pick what should travel. We set it up together with you, so no technical knowledge is needed, and after that it runs by itself.
Missing something you need?
Tell us what Lightspeed and GitHub should do for you. If it is not in here yet, that is usually because nobody has asked. We build on request and we reply within 24 hours.