Keep MplusKASSA and Slack updated automatically.
Today you open your shop’s admin, look at which orders came in and carry them over. With this connector, what happens in MplusKASSA lands in Slack by itself, in the shape Slack expects. Request it and you get access; you hear from us within 24 hours.
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 only hear something came in when someone happens to open the other system. Whatever really matters gets pasted into a channel by hand, or not at all.
What MplusKASSA to Slack saves you
- Get a Slack message for every new MplusKASSA order.
- Get a Slack message for every refund in MplusKASSA.
- Get a Slack message for every new MplusKASSA customer.
- Get a Slack message for every stock change in MplusKASSA.
What travels across the link
Everything this connector moves between MplusKASSA and Slack, and how often.
-
Notifications
to Slack automaticallyFrom this you get a short message in Slack in the channel you choose, one line on what happened, so you see it at once without logging in anywhere.
What each side expects
MplusKASSA and Slack do not describe the world the same way. This is what has to line up.
Slack
Slack needs to know which channel a notification belongs in. A message is only useful when one line says what happened, so nobody has to click through to learn whether it is urgent.
Setting it up
- 01
Request the connector
Request the MplusKASSA to Slack connector and get access. You hear from us within 24 hours.
- 02
We agree what should travel
Together we settle what should travel out of MplusKASSA. Slack needs to know which channel a notification belongs in. A message is only useful when one line says what happened, so nobody has to click through to learn whether it is urgent.
- 03
Test and switch on
You check the connector on a few test records before anything becomes final, then it runs by itself.
What you need
- A store you administer, with API access from its admin.
- A Slack workspace where you may add apps, plus the channel the notifications should land in.
Where it runs
Inside your Shopify admin, as an app. You sign in through Shopify, no separate account.
Request this connector: tell us what you need and we reply within 24 hours.
Common questions
Can you connect MplusKASSA to Slack?
Yes. Schakel connects through the official APIs of MplusKASSA and Slack, so you install nothing on your own server and nothing travels outside those two parties.
Can I choose which events send me a Slack message?
Yes. You decide which events from MplusKASSA produce a message, for instance a new order but not a stock change.
Which Slack channel do the notifications land in?
The channel you choose. You can also send different kinds of notification to different channels, so it does not become one big stream.
What happens on a refund or partial cancellation in MplusKASSA?
It comes across, so Slack matches what was actually settled and you correct nothing by hand.
What does connecting MplusKASSA and Slack 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 MplusKASSA sync with Slack?
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.
Do I get one Slack message per event or a summary?
By default it is one short message per event, one line on what is happening. If you would rather have a digest, we settle that when setting it up.
What if MplusKASSA or Slack 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.
Connect a different pair
MplusKASSA and Slack is one of many. Pick two systems and see what travels between them.
Missing something you need?
Tell us what MplusKASSA and Slack 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.