# How to add Slack to abas ERP

> Source: https://netray.co/integrations/abas-slack
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Integrations

## Short answer

Build a Slack app that talks to a small gateway in front of abas. Slash commands answer read-only questions, alerts post to channels, and interactive buttons carry approvals back through a whitelisted write path. Socket Mode lets an on-prem gateway work without opening inbound ports.

## System

abas ERP

## Capability

slack

## Intro

Slack is less common than Teams in classic abas customers, but it shows up in software-adjacent manufacturers, startups scaling a hardware product, and engineering groups that picked it years ago. Those teams still run abas for orders, stock and production, and the daily question is 'what is the status of X' asked in Slack and answered by someone opening the ERP.

A Slack app can answer the repeat questions itself and push the few events that matter, so people stop being the human interface to the ERP. It also gives a place to discuss an exception right next to the alert.

The main design choice is what the app may do. Start read-only, add a single approval type, and keep the ERP's own authority checks in force.

## Use Cases

### Slash command for order status

**Description:** Type /order 10234 and get a message with status, promised date, shipped quantity and next step, read from abas through the gateway.

### Stock check by item

**Description:** /stock 4711 returns on-hand, reserved and on-order quantities by warehouse so engineers can check before promising a build.

### Production exception alerts

**Description:** Post to a #production channel when a work order passes its planned finish or a component goes short, with a thread for the discussion.

### Purchase approval with buttons

**Description:** Send a block-kit message with Approve and Reject buttons for a purchase request and record the result back to abas.

### Customer escalation room

**Description:** When an order is flagged as critical, open or update a channel and post the order, lines and shipment state so everyone works from the same facts.

## System Surface

- EDP interface for session-based record access from a service process; libraries and exact behaviour depend on abas version.
- REST API on newer releases for customers, items, orders and stock, subject to your licence and installation.
- Infosystems for stable, role-aware lists such as open orders or shortages; they are the best candidates for slash command backends.
- abas user and role model that must be mapped to Slack user ids before accepting approvals.
- Scheduled scripts or an external scheduler for periodic digests; polling a change timestamp is a reliable fallback when no event hook is available.

## How It Works

### Create the Slack app

**Detail:** Define scopes (commands, chat:write, channels as needed), slash commands and interactivity. Prefer Socket Mode so the gateway opens an outbound WebSocket instead of exposing a URL.

### Write the gateway

**Detail:** A service with three or four whitelisted functions against abas: order_status, stock_by_item, list_exceptions, record_decision. No generic query passthrough.

### Map Slack users to abas users

**Detail:** Keep a table keyed by Slack user id. Reject commands from unmapped users and check ERP rights before returning sensitive values such as cost.

### Format with Block Kit

**Detail:** Return compact blocks: header, fields, and a button for the next action. Include the abas document number so people can open it in the client.

### Add alerts

**Detail:** A scheduler runs exception queries and posts only new items, tracking what it already announced to avoid repeats.

### Pilot and widen

**Detail:** Launch with two commands and one alert in one channel, review usage after two weeks, and then add approvals.

## Example Flows

### Engineer checks a build

**Trigger:** An engineer types /stock for a component in #engineering.

**Steps:**

- Slack sends the command to the gateway.
- The gateway maps the user and calls a stock query in abas.
- It returns an ephemeral message with on-hand, reserved and expected receipts.

**Result:** The engineer gets an answer in seconds, privately, with no ERP login.

### Short component alert

**Trigger:** The 06:00 job finds a component short for a work order starting within three days.

**Steps:**

- The gateway builds one message per work order with the shortage.
- It posts to #production and tags the planner on duty.
- The planner replies in the thread and clicks 'Expedite request', which creates a note on the purchase order.

**Result:** Shortages are discussed where the team works, and the ERP note keeps the trail.

## On Prem

Slack's Socket Mode fits an on-prem abas well: the gateway sits inside the plant network, uses a service account with read rights and a narrow write right, and connects outward to Slack over HTTPS and WebSocket. No inbound port needs to be opened. If Socket Mode is not allowed by policy, use a DMZ receiver that verifies Slack signatures and queues requests for the internal gateway to pull. Slack is a cloud service, so anything you post leaves your site. Keep messages to identifiers and status, avoid prices and drawings, and if you add a natural-language layer, host the model locally so question text and ERP results are not sent to an external AI provider.

## Security

- Verify Slack request signatures or use Socket Mode with a protected app-level token.
- Restrict the app to specific channels and user groups, and make sensitive commands ephemeral.
- Check authority in abas for every approval, not only in Slack.
- Store tokens in a secrets manager and rotate them; scope the bot to the minimum permissions.
- Review Slack retention and export settings, since posted ERP facts become searchable chat history.

## Options

### Workflow or automation tool with an HTTP connector

**Fit:** Alerts from a scheduled export or webhook when interactivity is not needed.

**Effort:** Days.

### Custom Slack app in-house

**Fit:** Slash commands, Block Kit and approvals tied to abas rights.

**Effort:** About 3 to 6 weeks including mapping and testing.

### Partner build such as Netray

**Fit:** You want a natural-language assistant in Slack on a private model, with the gateway and audit included.

**Effort:** A scoped pilot of a few weeks.

## Pitfalls

- Using a public channel for commands that reveal cost or margin.
- Slash commands that time out because the ERP query takes longer than three seconds; acknowledge first and respond later.
- No deduplication of alerts, leading to the same shortage posted nightly.
- Mapping users by display name instead of the stable Slack user id.
- Letting the bot grow into a general SQL console.

## Faq

### Is there a standard abas Slack app?

**Answer:** We are not aware of a standard one we can confirm for all versions. The usual approach is a custom Slack app using a gateway that reads abas via EDP or REST. Ask your abas partner whether an add-on exists for your release.

### Can Slack work with an on-prem abas?

**Answer:** Yes. Use Socket Mode or a DMZ queue so the gateway only makes outbound connections. The ERP does not need to be reachable from the internet.

### How do slash commands handle slow queries?

**Answer:** Slack expects an acknowledgement within about three seconds. Acknowledge immediately, run the abas query, and post the result using the response URL. For heavy lists, return the top results with a link rather than everything.

### Can people approve purchases in Slack?

**Answer:** Yes, with interactive buttons. The gateway must verify that the mapped abas user is allowed to approve that document and must check that the document has not changed since the message was sent.

### Should we pick Slack or Teams?

**Answer:** Use whichever your people already live in. Technically the pattern is the same: a gateway with whitelisted actions, identity mapping and outbound-only connectivity from the plant network.

## Search terms

abas slack integration, slack for abas erp, abas erp slack bot, abas erp slash command, abas erp alerts slack, abas erp approvals slack, slack notifications from abas, connect abas erp to slack, abas erp slack app, abas erp chatops

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json