Keep Trengo and Sendcloud updated automatically.
Today someone reads the message, and after that it still has to land somewhere else before anything happens. This connector fixes that, and we build it on request: what happens in Trengo lands in Sendcloud by itself, in the shape Sendcloud expects. Tell us what you need and we agree exactly what should travel.
What this connector takes off your hands
-
Today someone reads the message, and after that it still has to land somewhere else before anything happens.
-
Today you retype addresses into Sendcloud, pick the carrier per parcel, and afterwards paste the tracking number back into the system the order came from. When it gets busy that is the first thing to slip.
What Trengo to Sendcloud saves you
- Queue every new request via Trengo up in Sendcloud for shipping.
- Queue every appointment booked via Trengo up in Sendcloud for shipping.
- Queue a Trengo message left unanswered up in Sendcloud for shipping.
What travels across the link
Everything this connector moves between Trengo and Sendcloud, and how often.
-
Shipments
to Sendcloud automaticallyThis is queued up in Sendcloud ready to ship, with address and contents already attached, so all that is left is a label.
-
Labels
to Sendcloud automaticallyA shipping label follows in Sendcloud once the details are complete, so there is nothing to retype.
-
Inventory
to Sendcloud automaticallyStock levels travel along into Sendcloud, so warehouse and sales sit on the same count.
What each side expects
Trengo and Sendcloud do not describe the world the same way. This is what has to line up.
Sendcloud
Sendcloud wants a complete delivery address, a weight or parcel size and a shipping method. If the country and postcode combination is wrong no label comes out and the shipment stalls.
Setting it up
- 01
Request the connector
Let us know you want to link Trengo to Sendcloud. We get in touch within 24 hours with a timeline.
- 02
We agree what should travel
Together we settle what should travel out of Trengo. Sendcloud wants a complete delivery address, a weight or parcel size and a shipping method. If the country and postcode combination is wrong no label comes out and the shipment stalls.
- 03
We build and test
You see the connector run on a few test records before anything becomes final.
What you need
- An account you administer, and the inbox or channel involved.
- A Sendcloud account you administer. Under integrations in the settings you create the API credentials.
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 Trengo to Sendcloud?
Yes. Schakel connects through the official APIs of Trengo and Sendcloud, so you install nothing on your own server and nothing travels outside those two parties.
Does Sendcloud need a complete address, and what if it is wrong?
Sendcloud 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 Sendcloud myself?
Yes. Which carrier and shipping method Sendcloud uses you set there; Schakel only hands the shipment over complete.
How are the Trengo fields mapped to Sendcloud?
You set once which field from Trengo belongs where in Sendcloud. After that every new submission lands in the right place automatically.
What does connecting Trengo and Sendcloud 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 Trengo sync with Sendcloud?
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 someone fills in the Trengo form twice?
Then it checks by email whether the contact already exists, so you do not create a duplicate in Sendcloud.
What if Trengo or Sendcloud 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 Trengo and Sendcloud 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.