slack.md
For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs; this page is available as Markdown.
Slack
{% embed url="https://www.loom.com/share/ae6708a8668547dc9fd7a5dc27950011" %} Demo of Slack notifications in action {% endembed %}
Get notified in Slack of ION events to close the loop on critical issues and help your factory move faster. Any notification in ION can be output to Slack, allowing teams to bring users back to ION at key moments. This is important for onboarding new team members who need to develop the habit of using ION on a daily basis.
If a user is subscribed to a certain ION object and that object changes state, a user is mentioned in a comment, or assigned a task, ION will notify that user directly in Slack.
For example, if as user is mentioned are mentioned (@Alice) in a comment in ION that will send a direct message to Alice in Slack with a link back to ION where the location that the mention came from.
Examples of notification types within ION
Notification Types
ION has many notification types to configure - see the list below or reference the NotificationTypeEnum in the GraphQL API explorer. Your organization can choose to add these below notification types as values to the integration, which will then allow the integration to send them to Slack. See step 6 in the #set-upsection below on how to configure your organization Slack notifications.
| Keyword in Slack Integration | Notes |
|---|---|
approval_request |
The user is requested to approve an ION object, like a Purchase, Standard Step or Redline |
comment |
Someone commented on an object a user is subscribed to. |
datagrid_value_assigned |
The user is requested to review a datagrid cell signoff |
issue_approval_request_assigned |
The user is assigned to an approval request for an Issue |
issue_assigned |
The user is assigned to an Issue |
issue_created |
An Issue is created on an object subscribed by the user. |
issue_status_changed |
An Issue the user is subscribed to changes state |
mention |
The user is @ mentioned in a comment |
part_kit_assigned |
The user is assigned to a Kit |
part_kit_status_changed |
A Kit the user is subscribed to changes state |
procedure_released |
A Procedure the user is subscribed to is released |
procedure_status_changed |
A Procedure the user is subscribed to changes state |
review |
A user approved a Procedure. |
review_request |
The user is requested to review a Procedure |
run_assigned |
The user is assigned to a Run |
run_step_assigned |
The user is assigned to a step in a Run |
run_step_changed |
A Run step the user is subscribed to changes status |
run_step_field_assigned |
The user is requested to review a run step field signoff |
signoff |
The user is requested to sign off a field in a Run. |
purchase_order_assigned |
The user is assigned to a Purchase Order |
Set up
- Navigate to the Integrations page designated by the two arrows in the bottom lefthand corner of your screen.
Select Integrations in the Bottom Left Hand Corner
Set your Environment According to Where the API Keys were Generated