Keep Trengo and WeFact 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 WeFact by itself, in the shape WeFact 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 type the postings in by hand, pick the right account and VAT rate per line, and check afterwards whether it reconciles.
What Trengo to WeFact saves you
- Book every new request via Trengo straight into WeFact.
- Book every appointment booked via Trengo straight into WeFact.
- Book a Trengo message left unanswered straight into WeFact.
What travels across the link
Everything this connector moves between Trengo and WeFact, and how often.
-
Invoices
to WeFact automaticallyEvery sale becomes an invoice in WeFact with its own line items and the order number as reference, so you can trace it back without retyping.
-
Contacts
to WeFact automaticallyThe customer is recorded as a contact in WeFact or reused by email, so no duplicate relation appears.
-
VAT
to WeFact automaticallyThe VAT rate is set per line, and foreign sales get the rate of the destination country, ready for your OSS return.
What each side expects
Trengo and WeFact do not describe the world the same way. This is what has to line up.
WeFact
An accounting package wants to know, per line, which ledger account and VAT rate apply, and wants the customer on file as a relation.
Setting it up
- 01
Request the connector
Let us know you want to link Trengo to WeFact. 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. An accounting package wants to know, per line, which ledger account and VAT rate apply, and wants the customer on file as a relation.
- 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.
- An administration you administer, plus clarity on the ledger account you want used.
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 WeFact?
Yes. Schakel connects through the official APIs of Trengo and WeFact, so you install nothing on your own server and nothing travels outside those two parties.
Which VAT rate do my sales get in WeFact?
The rate is set per line: 21%, 9% or 0%. Sales to Belgium and other EU countries get the rate of the destination country, ready for your OSS return.
Are commission and fees booked separately in WeFact?
Yes. Commission, shipping and other fee types each land on their own ledger account in WeFact, rather than in one lump sum, so your margin stays readable.
How are the Trengo fields mapped to WeFact?
You set once which field from Trengo belongs where in WeFact. After that every new submission lands in the right place automatically.
What does connecting Trengo and WeFact 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 WeFact?
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 happens to a return or refund in WeFact?
A return becomes a credit invoice in WeFact for the amount actually refunded, not for the whole order, so nothing needs correcting afterwards.
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 WeFact.
Missing something you need?
Tell us what Trengo and WeFact 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.