# How to add Slack to ECI JobBOSS2 > Source: https://netray.co/integrations/jobboss-slack > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Integrations ## Short answer A Slack app for JobBOSS2 runs as a small service next to your shop server. It reads job, PO and inventory data from SQL Server, answers slash commands such as /job 20431, and posts interactive messages for approvals. Writes go through a review step rather than straight into the ERP. ## System ECI JobBOSS2 ## Capability slack ## Intro Some JobBOSS2 shops, especially younger ones with engineering or startup roots, run their day in Slack rather than Teams. The ERP stays on a desktop client, so a simple question like what is the status of job 20431 pulls someone away from their work to open it. Slack is good at quick, structured exchanges: a slash command, a thread, a button. That fits the questions people actually ask of an ERP in a job shop, where most are lookups of job status, material on hand or whether a PO has arrived. The design below keeps JobBOSS2 as the system of record, with Slack as a front door for lookups and a few controlled actions. ## Use Cases ### Slash command job lookup **Description:** Typing /job followed by a job number returns status, current operation, quantity complete and promised date as a compact message. ### Receiving heads-up **Description:** When a PO line is received against a job's material, post to the job channel so the programmer or machinist knows they can start. ### Inventory check **Description:** A /stock command takes a part or material number and returns quantity on hand and allocated, from the inventory tables. ### Overtime approval buttons **Description:** A planner requests weekend hours for a job and the production manager approves or declines from an interactive message. ### Per-customer channels **Description:** Create a channel for key accounts that gets milestone posts such as released, first article done and shipped. ## System Surface - SQL Server: the JobBOSS2 database is the main read path. Build views for jobs, operations, inventory and POs, and confirm table names against your installed version. - ECI JobBOSS2 API: where available under your license, use it for supported writes rather than touching tables directly. - Slack Events API and slash commands: your service needs a public HTTPS endpoint, so use a reverse proxy or relay in front of an internal host. - Job and PO notes: use these as the audit trail for anything Slack-originated so the ERP shows what happened. - Windows Task Scheduler or a service wrapper: simple ways to run the event poller on the shop server. ## How It Works ### Create a Slack app **Detail:** Register the app in your workspace with only the scopes you need, such as chat:write, commands and channel read for the channels it joins. ### Choose the transport **Detail:** Use Socket Mode if you cannot expose an inbound endpoint, which lets the service connect outward only. Otherwise use a verified HTTPS endpoint. ### Define read-only views **Detail:** Create views and a SQL login that returns only what each command needs. Return counts and statuses, not full cost rollups. ### Implement the commands **Detail:** Write handlers for /job and /stock that validate input, query the view with parameters, and format a short block message. ### Add the event poller **Detail:** Watch for received material, shipped jobs and slipped dates, and post to configured channels with deduplication. ### Build interactive approvals **Detail:** Use Block Kit buttons that carry an action ID. Resolve the Slack user to an approver list before acting. ### Record and review writes **Detail:** Store approvals in a staging table or as notes, and have a planner or the API apply the change under defined rules. ## Example Flows ### Machinist asks about material **Trigger:** A programmer types /stock 6061-1.5RD in the shop channel. **Steps:** - The service validates the item string and queries inventory. - It returns on hand, allocated and next expected PO date. - If a PO is due, the message links to the PO number. - The query is logged with the Slack user. **Result:** A one-line question answered in seconds without opening the ERP. ### Weekend overtime **Trigger:** A planner clicks Request overtime on a job message. **Steps:** - The service posts an approval message to the production manager with job, hours and reason. - The manager taps Approve or Decline. - The result is written as a job note and posted to the thread. - Payroll or scheduling changes remain a manual step by the right person. **Result:** A clear record of who approved, with no change to labor tables from chat. ## On Prem Slack is a cloud service, but your JobBOSS2 data does not have to move there in bulk. Keep SQL Server inside the shop network and run the Slack service on the same segment, using Socket Mode or a narrow relay so no database port is exposed. Remember that anything in a message is stored by Slack, so keep messages to identifiers and brief facts. If your company policy blocks cloud chat for customer data, use the same pattern with a self-hosted chat tool, or restrict the Slack integration to non-sensitive operational questions. ## Security - Verify Slack request signatures on every inbound call. - Grant the minimum OAuth scopes and install the app only to the channels that need it. - Use parameterized queries from the commands so user text can never alter SQL. - Map Slack users to roles on your side and check them before any action. - Do not post pricing, margin or controlled technical details in shared channels. ## Options ### Workflow tools such as Zapier or Make with a SQL connector **Fit:** A few simple alerts where data stays low sensitivity **Effort:** Days, with subscription cost and a need for a reachable SQL endpoint ### Build a Slack app in-house **Fit:** Shops with a Python or Node developer and a clear command list **Effort:** Two to five weeks ### Partner build with Netray **Fit:** Natural language questions over your data on a local model, plus governed approvals **Effort:** Scoped after reviewing your version and security needs ## Pitfalls - Slash command timeouts: Slack expects a reply within about three seconds, so acknowledge fast and post results asynchronously. - Exposing a public endpoint that talks straight to SQL Server. - Building commands that accept free-form SQL-like input. - Letting everyone in a channel see priced data because the bot is a member. ## Faq ### Is there a prebuilt JobBOSS2 Slack app? **Answer:** We do not know of an official one. ECI's offerings change, so ask your reseller, but most shops that do this build a small custom app or use a workflow tool with a SQL connector. ### Can Slack reach an on-prem SQL Server? **Answer:** Not directly and it should not. Run a service inside your network that connects outward to Slack with Socket Mode or sits behind a locked-down relay, and let that service query SQL Server. ### Can the app create jobs from Slack? **Answer:** It can create a request or a draft for review. We advise against automatic job creation from chat because routings, quantities and customer terms need verification. ### How much does it cost to run? **Answer:** The service itself is light and can run on the shop server. Costs are mostly development time and any Slack plan features you need, such as retention or SSO. ### Can I ask questions in natural language? **Answer:** Yes with a model that turns questions into safe read-only queries. Running it on a local model avoids sending job and customer data to an external provider. ## Search terms jobboss slack integration, slack for jobboss2, jobboss2 slack bot, slack slash command erp job status, eci jobboss slack alerts, jobboss slack notifications, job shop erp slack app, jobboss2 chat integration --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json