Connect your team with Slack — notifications and workflows right in chat.
This connection brings events from your saldia backend straight into your Slack channels. Instead of logging into saldiaCore again and again, new orders, incoming support tickets or other important events arrive as messages right where your team already spends its day. Everyone sees what's happening at a glance and can react in the thread or hand the task to the right person.
The connection runs through saldiaConnect, the integration layer between saldia and third-party systems. You decide which events go into which channel, and the saldia team sets the connection up together with you. One thing to keep in mind: here Slack is an internal tool for your team, not for your customers – it's about fast internal workflows, not customer communication. Support comes from Switzerland.
New orders straight into the team channel
Your saldiaCore is running, and every new order should appear in a channel like #orders. The moment an order comes in, your warehouse and shipping team sees it in Slack without keeping the backend open all day. Especially during busy periods you react faster to large or urgent orders and coordinate right in the thread on who picks and packs.
Support tickets in the right channel
Incoming support tickets from saldiaCore's ticketing shouldn't slip through. Through the connection, every new ticket lands in a channel like #support, so your team sees it immediately and sorts out in the thread who takes it on. That shortens response times without anyone having to keep ticketing open all day. You still reply inside saldiaCore — Slack serves as the fast internal notification.
Keeping an eye on key events
You don't want to see every event, just the ones that matter? You can set up a dedicated channel like #important that receives selected events from saldiaCore — for example a particularly large order or an escalated ticket. Your team stays in the loop without drowning in noise. Exactly which events get pushed is something you define together with the saldia team.
The connection runs through saldiaConnect. Certain events in your saldia backend — such as a new order or a new support ticket in saldiaCore — are sent as a message into the Slack channel you choose. The flow goes from saldia to Slack: saldia reports, your team reacts in Slack.
The connection runs through saldiaConnect, which bundles the events from saldiaCore — the all-in-one platform with ERP, CRM and ticketing. Typical sources are events like orders or support tickets. What makes sense for you depends on your setup — best looked at together with the saldia team.
No. This connection is a purely internal tool for your team. The messages land only in your Slack channels, not with your customers. For communicating with customers you continue to use the dedicated channels in your saldia products.
You don't have to handle this alone. The saldia team sets up the connection via saldiaConnect with you and discusses which events should go into which channel. Just get in touch with saldia support.
Ready to bring your key saldia events into Slack? Reach out to the saldia team — we'll set up saldiaConnect together with you so your team can react faster.
These saldia products work together with this integration.
Activate the integration directly in your saldia product's backend, or contact us if you need help.
