Keep Zalando and GitHub updated automatically.
Today you sign in to the seller account, look at what sold and carry it over by hand. What you already processed you track somewhere else. This connector fixes that, and we build it on request: what happens in Zalando 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 sign in to the seller account, look at what sold and carry it over by hand. What you already processed you track somewhere else.
-
Today you create the task or the row yourself, or you just remember it and that fails eventually.
What Zalando to GitHub saves you
- Turn every new Zalando order into a GitHub task automatically.
- Turn every Zalando return into a GitHub task automatically.
- Turn every Zalando payout into a GitHub task automatically.
- Turn stock running low on Zalando into a GitHub task automatically.
- Turn every cancellation on Zalando into a GitHub task automatically.
What travels across the link
Everything this connector moves between Zalando 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
Zalando and GitHub do not describe the world the same way. This is what has to line up.
Zalando
A marketplace supplies orders with their own order number and their own lines, plus returns and cancellations that arrive separately.
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 Zalando 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 Zalando. 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 seller account with API access, created from within the account itself.
- An account with edit rights, and the list or project it should land in.
Where it runs
On app.schakel.app, with your own Schakel account. No webshop required.
We build this connector on request. Tell us what you need and we reply within 24 hours.
Common questions
Can you connect Zalando to GitHub?
Yes. Schakel connects through the official APIs of Zalando 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 Zalando come along, so a task or row in GitHub has just enough context.
Do I still have to log into Zalando once the connector runs?
No. Once it runs, everything you now look up in the Zalando seller account arrives in GitHub by itself. You only open Zalando when you want to check something yourself.
What does connecting Zalando 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 Zalando 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.
Does the connector also pick up Zalando returns and cancellations?
Yes. Besides new orders, Schakel also sees returns and cancellations on Zalando, so GitHub does not lag behind what actually sold.
What if Zalando 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.
Missing something you need?
Tell us what Zalando 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.