How to add Slack to Global Shop Solutions
Short answer
Slack connects to Global Shop Solutions through a small app that your bridge service backs: slash commands for lookups, interactive messages for approvals and incoming alerts for exceptions. The bridge reads the ERP through ODBC or a supported interface and talks to Slack over outbound HTTPS or Socket Mode.
Some Global Shop customers, especially newer or tech-heavy shops with engineering teams, run Slack rather than Teams. The ERP sits in the plant, the conversation sits in Slack, and the two never meet. Planners paste job numbers into channels and someone else looks them up.
A Slack app can close that gap in a lightweight way. It does not replace ERP screens, but it makes the repetitive questions and one-click decisions much cheaper.
The key design choice is Socket Mode versus HTTP events. For an on-prem ERP behind a firewall, Socket Mode avoids exposing any public URL, which suits many plants.
What teams use it for
Slash command job lookup
Type /job 24-1182 and get current operation, work center, due date and holds, read from the job tables.
Part availability check
/stock PN returns on hand, allocated, on order and next receipt for a part across locations.
Interactive PO approvals
Post a Block Kit message with Approve and Reject; the click goes through a gated approval path.
Hot-job and hold alerts
Channel alerts for expedited jobs, quality holds or machine-down impacts on committed orders.
Shift handoff summaries
At shift end, post jobs in process, late ones and open issues from the ERP to the plant channel.
Global Shop Solutions integration surface
- Read access via ODBC to the ERP database, commonly a Pervasive/Actian-style engine on on-prem installs. Verify for your version.
- Any vendor-supported API or web service available under your licence; ask your Global Shop contact which one applies.
- Scheduled report output to a share for digests that do not need live data.
- ERP user records for mapping Slack users by email.
- Job, operation, work center, purchase order and inventory tables are the usual read targets. Exact table names vary by release, so use the vendor schema documentation.
How it works
- 1
Create the Slack app
Define slash commands, bot scopes such as chat:write and commands, and enable interactivity. Install to the workspace after admin approval.
- 2
Choose Socket Mode
The bridge opens an outbound WebSocket to Slack, so no inbound port or public URL is required for the plant network.
- 3
Implement vetted queries
Each slash command maps to a parameterised read-only query. Do not pass raw text into SQL.
- 4
Map Slack users to ERP users
Match on verified email. Restrict commands by role and channel.
- 5
Add interactive approvals
Use Block Kit buttons with an action ID and document key. On click, re-read the document, check the approver, then create the approval record.
- 6
Add alert producers
Scheduled checks post to channels by rule, with throttling and de-duplication so a recurring condition posts once.
Example flows
Planner checks a job in channel
Trigger: A planner types /job with a job number.
- Bridge validates the user and the job number format.
- It queries the job header and current operation.
- It replies ephemerally with status, due date and any holds.
Result: The answer reaches only the requester, and the ERP was queried read-only.
Expedite alert
Trigger: A sales order line is flagged as rush and the job is not yet released.
- Alert producer detects the condition.
- It posts to the planning channel with job, customer and promise date.
- A planner clicks Acknowledge, which records the acknowledgement in a log.
Result: Rush work is visible to the right people within minutes.
Keeping data on-prem
Slack is cloud-hosted, so keep the ERP data path local: a bridge in the plant network, a read-only database account, and Socket Mode so the plant opens no inbound port. Limit what is sent into Slack to identifiers and brief status text; treat message content as stored by Slack under your workspace retention rules. If you want natural-language commands, run a local open-weight model on a GPU server that translates the request into one of your approved queries, so ERP data is never sent to an external model. For defense or export-controlled work, keep controlled data out of Slack channels entirely and use deep links to ERP screens instead.
Security checklist
- Verify Slack signatures when using HTTP events; with Socket Mode, protect the app-level token as a secret.
- Use ephemeral responses for sensitive lookups so channel members do not see them.
- Limit commands by channel and by role; log user, command and result size.
- Give the bridge only SELECT rights, plus a separate path for approvals.
- Rotate tokens and store them in a secrets manager, not in config files on the ERP server.
Ways to get it done
Slack Workflow Builder with a CSV or webhook feed
Effort: Hours to days.
Simple scheduled digests and alert posts.
Custom Slack app with a bridge service
Effort: Two to four weeks including security review.
Slash commands and interactive approvals tied to ERP data.
Partner build with Netray
Effort: Scoped pilot, usually read-only first.
You want grounded natural-language answers, local models and an approval audit trail.
Pitfalls
- !Slash commands must respond within a few seconds; acknowledge immediately and follow up for slow queries.
- !Running heavy queries against the production database during shifts.
- !Posting alerts without throttling, creating noise that teams mute.
- !Using a personal account's token for the app.
- !Forgetting that edited or deleted ERP records can leave stale buttons in old messages.
Frequently asked questions
Does Global Shop Solutions integrate with Slack out of the box?
We are not aware of a native Slack integration. Ask your Global Shop account team about notification options in your release. Most customers build a small bridge that reads the ERP and posts through the Slack API.
Do we need to open firewall ports?
Not if you use Socket Mode. The bridge makes an outbound connection to Slack. If you choose HTTP events instead, you need a public HTTPS endpoint, which is usually placed in a DMZ or a cloud function.
Can Slack approve purchase orders in the ERP?
It can trigger an approval, but write-back should run through a supported ERP path with the approver identity checked and logged. Avoid direct table updates from the Slack app.
Is Slack suitable for ITAR or CUI data?
Treat it with caution. Unless your Slack tenancy meets your compliance requirement, send only non-controlled identifiers and link to the ERP for detail. Your compliance officer should decide.
Can AI answer free-text questions in Slack?
Yes. A model can map a question to an approved query. Hosting an open-weight model on-prem keeps the ERP content local, and only the short answer goes to Slack.
Want Slack working on your Global Shop Solutions?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment