How to connect Slack to SAP Business ByDesign
Short answer
Create a Slack app with slash commands and interactive messages, backed by a service that calls ByDesign through a communication arrangement. Reads use report-based OData feeds or web services; writes such as approvals call narrowly scoped services and are logged to a named user.
Slack tends to show up in ByDesign companies that are younger, software-adjacent or distribution-led, where ops and sales already live in Slack and the ERP is one of the few systems outside it. The result is a familiar pattern: someone asks in a channel whether an order shipped, and someone else logs into ByDesign to answer.
A Slack app that answers those questions, pushes exceptions and handles routine approvals turns the channel into a thin console for ByDesign. The aim is fewer logins for casual users and faster response on things that otherwise sit.
ByDesign is SaaS-only, so all of this runs through its supported interfaces: communication scenarios, custom services from the Cloud Application Studio, and report feeds. There is no database to query and no on-prem component to install.
What teams use it for
Slash command for order status
Typing a customer name or order number returns status, promised date and delivery progress, read from a report feed or sales order service.
Inventory check by SKU
A slash command returns available, reserved and in-transit quantity for a material per warehouse, which sales can use before promising a date.
Interactive approvals
Block Kit messages with Approve and Reject for purchase requests, expense reports or supplier invoices, writing the decision back to the workflow.
Shipment alerts into the customer channel
For shared channels with key accounts, post a short update when a delivery is dispatched.
Quote request intake
A message action on a customer email or a form creates a draft sales quotation for sales to price.
Daily ops digest
A scheduled post summarising late purchase orders, open production orders and unbilled deliveries.
SAP Business ByDesign integration surface
- SOAP web services exposed via Communication Scenarios, with the Slack backend represented as a communication system and a technical communication user.
- Business Analytics report feeds consumed as OData for read-only queries, which are quick to set up and keep write access out of the picture.
- Custom OData and web services built in the Cloud Application Studio for exact, minimal operations such as completing a specific task or creating a draft quote.
- Workflow rules and SDK events that can call a webhook endpoint on status changes, as an alternative to polling.
- Service names, scenario IDs and field names differ by release, so use the Service Explorer in your tenant as the source of truth.
How it works
- 1
Create the Slack app
Enable slash commands, interactivity and an events or incoming webhook endpoint. Install to the workspace with the narrowest scopes needed.
- 2
Stand up a request-handling service
Slack expects a response within three seconds, so acknowledge immediately and post the result asynchronously using the response URL.
- 3
Provision ByDesign access
Create a communication system and user, then an arrangement covering only the scenarios you plan to use. Start with read-only.
- 4
Map Slack users
Match Slack user email to ByDesign employee or business user for authority checks, and refuse commands from unmapped users.
- 5
Implement commands one at a time
Begin with order status and stock check, add approvals after you have trust in logging and mapping.
- 6
Add scheduled digests and alerts
Use a scheduler to run report queries and post to specific channels, with thresholds and de-duplication so the same exception is not posted daily.
Example flows
Where is my order
Trigger: A salesperson types /order ACME-4471 in a sales channel.
- The service acknowledges the command and looks up the sales order via a service call.
- It reads delivery status and expected goods issue date.
- It replies privately to the requester with status and a link to the ByDesign document.
Result: The question is answered in seconds, and the order desk is not interrupted.
Approve a supplier invoice
Trigger: An invoice enters approval with an amount over a threshold.
- The workflow calls the service with invoice ID, supplier, amount and PO reference.
- The service DMs the approver a Block Kit message.
- On Approve, it checks the mapped user, completes the task, and edits the message to show who decided and when.
Result: Invoices stop waiting for someone to open ByDesign, with a decision trail stored in both systems.
Keeping data on-prem
The ByDesign side cannot be on-prem, but the Slack service can sit in your own network if you use Socket Mode or expose a locked-down endpoint. Any AI that interprets free-text questions should run on a self-hosted open-weight model so that customer names, pricing and margins in prompts do not leave your environment. Constrain the model to a fixed list of read-only queries rather than letting it compose arbitrary calls.
Security checklist
- Verify Slack request signatures on every call, and reject anything older than five minutes.
- Never post margins, cost prices or personal data to broad public channels; use ephemeral or direct messages.
- Separate read and write arrangements in ByDesign and keep write credentials in a secrets vault.
- Check each action against the mapped user's authority before using the technical user to write.
- Log commands, parameters and results with Slack user ID for audit.
Ways to get it done
Zapier or Make style automation
Effort: Hours to days, limited for approvals and mapping.
Fine for simple outbound alerts if you can expose the data through a webhook or feed.
Custom Slack app with a thin ByDesign service
Effort: 2 to 5 weeks.
The right level for slash commands, approvals and digests with audit.
Partner build with a private AI layer
Effort: 4 to 8 weeks.
When people should ask plain-English questions and data must stay in your boundary.
Pitfalls
- !The three-second response limit breaks slow ByDesign calls; always acknowledge first.
- !Public channels leak data over time as membership grows; default to private replies.
- !A single technical user makes every action look the same in ByDesign; include the Slack user in comments.
- !Report feeds can be slow on large datasets; add filters and paging.
- !Slack app tokens and signing secrets expire or rotate with workspace admin changes; monitor for auth errors.
Frequently asked questions
Is there a ready-made Slack connector for SAP Business ByDesign?
I am not aware of a standard one I could vouch for. Third-party integration platforms may offer ByDesign connectors, but for approvals and per-user authority checks a small custom Slack app over web services is usually more reliable.
Can Slack trigger a ByDesign transaction?
Yes, through a web service or custom OData service. Good candidates are approvals, comments and draft documents. Posting final orders or invoices directly from a chat is riskier and normally needs a review step.
How do I stop sensitive data appearing in Slack?
Limit what the commands return, use ephemeral or direct messages, and scope channel membership. Put links to ByDesign documents in messages instead of copying full details, since access control then stays with ByDesign.
Can Slack and Microsoft Teams both be used?
Yes. Build the ByDesign service layer once and add thin adapters for each chat platform. That avoids duplicating mapping, authority checks and logging.
Is natural language search possible?
Yes, by adding a model that routes a question to approved read-only queries. For commercially sensitive data, running that model on your own infrastructure is a sound choice, and the model should never have write access.
More for SAP Business ByDesign
Want Slack working on your SAP Business ByDesign?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment