How to add Slack to IFS Cloud
Short answer
Connect Slack to IFS Cloud with a Slack app that posts alerts from IFS Business Events delivered by IFS Connect, offers slash commands that read IFS projections, and sends interactive messages for approvals. A small service sits between them, so IFS credentials never reach Slack.
Slack is less common than Teams among IFS Cloud customers, but it is the default for plenty of engineering-led manufacturers, aerospace startups and technology-heavy service businesses that adopted IFS for asset-heavy or project work. Those teams talk in Slack all day and treat Aurena as a system of record they visit when forced.
The goal is rarely to replicate IFS in chat. It is to move the few moments where a person is the bottleneck into a place they will see: a part that is late, a work task that is blocked, a quote that needs a margin sign-off. Slash commands also help people find answers, such as the status of an order, without navigating Aurena.
Below is a pragmatic architecture based on supported IFS integration points, with attention to Slack's rules on app scopes, rate limits and workspace data retention.
What teams use it for
Slash command order lookup
A command such as /ifs order 12345 returns status, promised date and last shipment for a customer order through a read projection.
Late supplier alert channel
A channel receives a message for each purchase order line that passes its promised date, with a button to log that the buyer has chased.
Project milestone notices
Project teams get messages when milestones change status or when forecast cost moves outside tolerance.
Engineering change visibility
Notify the engineering and planning channels when an engineering change reaches released state, with affected parts listed.
Asset downtime alerts
Maintenance channels receive a message when a critical equipment object gets a fault work request, with severity and location.
Quote margin approvals
Sales leaders receive an interactive message with quote value and margin, and approve or return it in place.
IFS Cloud integration surface
- OData projections under the projection/v1 path serve both slash command reads and approval actions. Confirm exact projection and entity names for your release in API Explorer.
- Business Events with IFS Connect are the push mechanism. Configure the event, then route through a REST connector to your service, relying on the queue for retry.
- IFS identity and service clients: use a service client with OpenID Connect client credentials, with permission sets scoped to the data the app serves.
- Person and contact data: IFS keeps user and person records, so a Slack email can be matched to an IFS identity for rights checks.
- Aurena links: messages can deep link to pages for deeper work.
How it works
- 1
Create the Slack app
Define bot scopes for posting and commands, enable interactivity and slash commands, and choose Socket Mode if you cannot expose a public URL.
- 2
Stand up the relay service
A service verifies Slack signatures, authenticates to IFS with its service client, and holds the mapping between Slack users and IFS persons.
- 3
Wire IFS events
Route selected Business Events through IFS Connect to the relay. Use a message queue so a relay outage does not lose events.
- 4
Design the messages
Use Block Kit with a short summary, key figures and buttons. Keep an opaque id in the action value that points to server-side state.
- 5
Implement slash commands
Resolve the caller, check their IFS rights, query the projection with filters, and answer ephemerally so only they see it.
- 6
Handle button actions
Check the user's right to act, call the projection action, and update the original message with the result.
- 7
Observe and throttle
Respect Slack rate limits, batch noisy events into digests and keep a log keyed by IFS record.
Example flows
Order lookup by slash command
Trigger: A sales engineer types /ifs order with a number
- Slack posts the command to the relay
- Relay maps the user to an IFS person and checks access
- Relay queries the customer order projection with a filter
- Relay returns an ephemeral message with status, lines and promised dates
Result: Answers in seconds without opening Aurena, scoped to what the user could see anyway.
Quote margin approval
Trigger: A quote falls below target margin
- Event or poll identifies the quote
- Interactive message goes to the sales director with value, margin and customer history
- Director selects Approve or Send back with a note
- Relay executes the action and posts the outcome in the deal thread
Result: Margin exceptions get decisions inside the sales conversation.
Fault request alert
Trigger: A critical equipment fault request is created
- Business Event reaches the relay
- Relay enriches with equipment location and open tasks
- Message posts to the maintenance channel with Claim button
- First claimant becomes the owner and the work task is updated
Result: A named technician owns each critical fault within minutes.
Keeping data on-prem
If IFS Cloud runs in your datacenter or a private cloud, host the relay beside it and use Slack Socket Mode so no inbound port is opened. Slack itself stores message content in its cloud, so keep controlled data out of messages: send identifiers and deep links, and make the user authenticate to Aurena for detail. For conversational questions about IFS data, point an on-prem retrieval service built on an open-weight model at the projections, and have it answer through the same Slack app without transmitting records to a public model.
Security checklist
- Verify Slack request signatures and timestamps on every call.
- Match Slack users to IFS persons by verified email, and refuse unmatched users.
- Store IFS credentials only in your secret store, never in Slack or in message values.
- Use ephemeral replies for sensitive lookups and avoid posting figures to wide channels.
- Set Slack retention and export policies with security staff before launch.
Ways to get it done
Workflow builder or automation platform calling IFS REST
Effort: Days
Basic alerts, low rights sensitivity
Custom Slack app with a relay service
Effort: Around six to eight weeks for a first scope
Slash commands, approvals and per-user rights
Partner build with Netray
Effort: Phased, starting with read-only questions
Natural-language questions over IFS data and on-prem models
Pitfalls
- !Letting the app use one broad IFS account so every Slack user can see everything.
- !Slash commands that time out because the projection query is slow; acknowledge in three seconds and respond later.
- !Posting an alert per event with no digesting, which trains people to mute the channel.
- !Embedding record ids and amounts in button values that can be tampered with.
- !Assuming event names and fields stay the same after an IFS Cloud release update.
Frequently asked questions
Does IFS Cloud integrate with Slack out of the box?
We cannot point to a standard, complete IFS to Slack connector across releases. Generic webhooks and IFS Connect make a custom or marketplace-based link practical. Check your release documentation and partner catalog, then compare with building a small relay.
Can Slack approvals be trusted as an audit record?
They can if the relay maps the Slack user to an IFS person, checks rights, executes the approval in IFS under that identity, and logs the request id. The IFS approval history remains the system record, with Slack as the interface.
How do we avoid exposing sensitive order data in Slack?
Send only identifiers, status words and links. Use ephemeral responses for lookups and require sign-in to Aurena for detail. Decide with security which fields may appear, and keep export-controlled content out entirely.
Should we use Socket Mode?
Use it when you cannot expose a public HTTPS endpoint, such as for a relay inside a private network. It uses an outbound websocket from your service to Slack. Public request URLs are simpler to scale when your environment allows them.
Can we ask free-form questions about IFS data in Slack?
Yes, with a retrieval layer. It converts the question into allowed projection queries or document searches, applies the asker's IFS rights and returns a grounded answer. Open-weight models on your own hardware can do this without sending data to a public service.
Want Slack working on your IFS Cloud?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment