Connect IFS Cloud to email and chat
Two patterns that link IFS to Gmail, Outlook, Slack and Teams.
The short answer
Events go out to chat. Decisions come back into IFS.
Two ways IFS connects to email and chat
Events out of IFS
- IFSWork order assigned
- FlowAdds site and asset
- TeamsTells the technician
Actions into IFS
- OutlookAn invoice arrives
- AgentReads and checks it
- IFSCreates the invoice
Connect by signing in, not with API keys
With API keys, an administrator creates and hands over credentials, mailbox by mailbox.
With one click, the person building the flow signs in and approves the scopes.
No tickets, and no shared secrets.
Six flows worth building first
| Flow | Starts when | Lands in |
|---|---|---|
| Technician alert | A work order is assigned | Teams |
| Credit block | An order is blocked for credit | Slack |
| Invoice mismatch | An invoice fails its match | Outlook, with an approval |
| Invoice capture | A PDF reaches the inbox | IFS |
| Overdue digest | Each morning, per site | Teams |
| New inquiry | A sales email arrives | IFS and Slack |
Roll it out in three steps
Notifications first
Events out of IFS, for the first weeks. Nothing is written.
One write, behind a yes
The first action into IFS, approved before it posts.
Then widen
Next flows from templates, on the same connections.
Questions before you connect
How do one-click connections differ from API keys?
With API keys, an administrator registers an app, creates credentials and hands them to whoever builds the flow, then owns rotating and revoking them. With a one-click connection, the user signs in to their own Google, Microsoft or Slack account and approves the scopes. NgageFlow connects Gmail, Outlook, Slack and Teams this way, stores the tokens encrypted and refreshes them, and each connection can be revoked on its own.
Which scopes should we grant?
The narrowest that does the job. Reading a shared mailbox needs no send rights, and posting to a channel does not need the rest of the workspace. Narrow scopes keep the consent screen honest and the review short.
Who can use a connection?
The project it belongs to. In NgageFlow, connections are scoped to projects with role-based access, so the finance mailbox powers finance flows and nobody else’s.
Do alert recipients need IFS access?
No. They work in Teams, Slack or email. Reads and writes in IFS run within the IFS permissions of the person the flow acts for. How that maps to your IFS licences is a question for your IFS account team.
Where do mail and tokens live?
In the environment NgageFlow runs in: your own cloud, or managed by EX10. Keep channels tidy as well: a credit block alert belongs in a finance channel, not the company-wide one.
Does this work with IBM Maximo and SAP?
Yes. IBM Maximo, IFS and SAP work out of the box, through each ERP’s official interfaces, and one flow can use two of them, for example the asset in IFS and its cost in SAP. For any other application, including a homegrown one, we teach Ngage how it works in weeks. This guide uses IFS terms because it is written for IFS teams.
How soon can we try it on our IFS?
On IFS, a flow can be live in hours, depending on access to your test environment and the scope.
Automate an alert your team checks by hand
Describe it in a sentence or two. We run it with you, live, in a safe test setup.