Keep GitHub and MyParcel updated automatically.
Today it sits in a list or a spreadsheet, and afterwards someone retypes it into the system that actually has to act on it. This connector fixes that, and we build it on request: what happens in GitHub lands in MyParcel by itself, in the shape MyParcel expects. Tell us what you need and we agree exactly what should travel.
What this connector takes off your hands
-
Today it sits in a list or a spreadsheet, and afterwards someone retypes it into the system that actually has to act on it.
-
Today you copy the details over by hand, then paste the result back into the system it came from.
What GitHub to MyParcel saves you
- Queue every task you finish in GitHub up in MyParcel for shipping.
- Queue every new row in GitHub up in MyParcel for shipping.
What travels across the link
Everything this connector moves between GitHub and MyParcel, and how often.
-
Shipments
to MyParcel automaticallyThis is queued up in MyParcel ready to ship, with address and contents already attached, so all that is left is a label.
-
Labels
to MyParcel automaticallyA shipping label follows in MyParcel once the details are complete, so there is nothing to retype.
-
Inventory
to MyParcel automaticallyStock levels travel along into MyParcel, so warehouse and sales sit on the same count.
What each side expects
GitHub and MyParcel do not describe the world the same way. This is what has to line up.
MyParcel
An operational system wants complete data: an address that is right, a product that exists, and clarity on exactly what goes out the door.
Setting it up
- 01
Request the connector
Let us know you want to link GitHub to MyParcel. We get in touch within 24 hours with a timeline.
- 02
We agree what should travel
Together we settle what should travel out of GitHub. An operational system wants complete data: an address that is right, a product that exists, and clarity on exactly what goes out the door.
- 03
We build and test
You see the connector run on a few test records before anything becomes final.
What you need
- An account with edit rights, and the list or project it should land in.
- An account you administer, with API credentials from its settings.
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 GitHub to MyParcel?
Yes. Schakel connects through the official APIs of GitHub and MyParcel, so you install nothing on your own server and nothing travels outside those two parties.
Does MyParcel need a complete address, and what if it is wrong?
MyParcel needs a full delivery address to make a label. If the country and postcode do not match up, that shipment is held and shows in the log, rather than a wrong label coming out.
Can I choose the carrier in MyParcel myself?
Yes. Which carrier and shipping method MyParcel uses you set there; Schakel only hands the shipment over complete.
From what moment in GitHub does something reach MyParcel?
As soon as you add or finish the row or task in GitHub that you chose as the trigger, it reaches MyParcel.
What does connecting GitHub and MyParcel 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 GitHub sync with MyParcel?
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 GitHub or MyParcel 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 GitHub to MyParcel?
You give Schakel access to GitHub and MyParcel 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 GitHub and MyParcel 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.