Process → team update
Send relevant process updates to the agreed team or communication channel.
All integrations
Workplace & access
Slack
Have a process post a targeted Slack message. Give the team context and a link to the source record.
From product to process
How to use the integration
Exceptions → tasks
Route missing information or discrepancies to the team responsible for follow-up.
Combine into one controlled process
Data → rules → execution-
Combine
Process status + team + channel
-
Determine & check
Determine which update matters
-
Execute & report back
Send Slack message · Link to request · Track handling in the source system
Check sources and rules, test changes and track the outcome. Manual tasks get an owner and confirmation.
Build visually. Manage easily.
Reuse building blocks, adapt your process and test the change. Manage it yourself, together with us or let Scope4mation take care of it.
More process examples & technical details
The work between your applications
Change requested.
Who handles the next steps?
Service Automation Suite connects Slack with your other applications, people and rules. Keep data aligned, work moving and outstanding actions visible.
A change, request or alert
Service Automation Suite
Data, people, assets and relationships on one foundation.
- Compare
- What exists? What should exist?
- Determine what is needed
- Matrix · policy · legal requirements
- Coordinate the next steps
- Checks · tasks · approvals · actions
Execution ↔ feedback
Your people and tools
Slack
For example. Also with other teams, suppliers and applications.
Verify. Inform. Report.
What is complete? Who needs to act? Which exception needs attention?
Alerts & follow-up
The right update, in the wrong channel.
Have a process post a targeted Slack message. Give the team context and a link to the source record.
Combine data and apply rules
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
SlackRelevant data or workflow status
Update, execute and record outcomes
Choose the relevant event
A change or process status determines when a team needs a message.
Add context in the channel
Post a targeted message with the necessary context and a link to the source record.
Keep work with its source
The team sees where action is needed. Requests and execution remain in the agreed work system.
Handover to service
The customer does not need to start over.
Connect available customer, project or case data to the delivery team. Keep the original request identifiable.
Combine data and apply rules
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
SlackRelevant data or workflow status
Update, execute and record outcomes
Choose the handover moment
Choose the status or event that triggers the handover and the context required.
Prepare focused work
Connect relevant data to a request or task for the responsible team.
Return progress
Show the original team what has been handled and which information is still missing.
Under the hood
How to connect, test and manage the integration.
For administrators who want to understand how it works: connect Slack to your other applications, map the data and use the response in the next step. Configure it centrally in Service Automation Suite.
Example configuration · shaped by your process
Execute and verify an account or group action
Connect and test
API ComposerChoose the API method, URL and authentication. Manage the host and credentials in an environment. Test a request in Discovery and inspect the fields actually returned by the API.
Combine and compare
Data Flow ComposerSelect fields, translate codes and relate records using shared data. Compare source and target to identify new, changed or incomplete records.
Execute and use the response
API ComposerBuild the request body from validated data and inspect Body Preview before testing. Use the result ID in Data Context for the next request or save output to an entity. Configure write-back separately.
Recognise errors and follow up deliberately
API ComposerConfigure error rules by HTTP code and/or message. A temporary API failure can use bounded retries. A missing relationship or rejection needs another route: record the cause and configure a verification task for the appropriate team, for example.
Which data do you maintain?
An example configuration, not fixed field names or a mandatory combination.
- Person reference and account ID
- Connect the source person to the correct account using verified identifiers.
- Approved role and desired groups
- Compare the agreed matrix with available account data and configure additions and revocations separately.
- Account action result
- Use the API response and configured follow-up check to report back to HR or TOPdesk, for example.
Sent ≠ processed. Use the response and agreed validation to determine the next step.
Need to publish data yourself?
Use Endpoint Composer to publish a configured Service Automation Suite data object. Choose read and write methods and security profiles so a customer can retrieve agreed service data or a supplier can submit information, for example. Configure data selection and subsequent processing separately.
Endpoint ComposerFrom data to a complete process?
Combine the integration with a form, a shared matrix, a review or collaboration between service teams. For example, an approved request leads to execution in Microsoft Entra, a ValidSign signature request and feedback in TOPdesk. Your process determines the steps needed; not every use case requires all these components.
Explore the connected building blocksBeyond the first integration.
Use the same data and rules in your next process.
Start with one use case. Connect customer, employee and asset data, for example, and agree which source is authoritative. Reuse those relationships, a matrix where needed and configured actions in the next workflow. Agree who maintains the data and rules. Expand without repeatedly connecting and maintaining the same information.
Signature declined. Keep the process moving.
A request awaits a ValidSign signature. Declining, expiry and technical failure each need different handling.
- Combine
- Link the request, signing request and document. Read the available status and apply agreed conditions to determine the next action.
- The outcome determines what follows
- Signed: process the document and confirm the activity. Declined: route the reason to the owner. Temporary technical failure: retry only under the configured error rule.
- The benefit
- Appropriate follow-up for each outcome without counting a sent signing request as completed work.
A replacement laptop without losing context.
An employee receives a replacement device. The old asset, new record and open service or security tickets must remain connected.
- Combine
- Use the central relationship between owner and device identifiers. Combine handover, technical inventory and return with existing tickets.
- The outcome determines what follows
- Receipt confirmed: update ownership and relationships. Old device missing or uncertain match: start a targeted review instead of overwriting historical records.
- The benefit
- Current records and a traceable handover even when a management tool uses different names.
Temporary access, with the end handled too.
Additional access is approved for a limited period. A checkbox alone does not preserve why, for whom and until when.
- Combine
- Connect identity, approval, expiry date and the available access action. Reuse the same data for a scheduled follow-up check.
- The outcome determines what follows
- Revocation confirmed: record the result. Extension requested: ask for a new decision. Not revoked: raise the exception with the authorised group rather than silently completing it.
- The benefit
- Fewer forgotten exceptions and a traceable relationship between approval and actual access.
Your process needs more than a standard action?
Configure the missing API request, input and output in API Composer. Use its response in the next step and combine it with data tables, forms and automations. Extend the same product and reuse the configured building blocks.
Use Service Automation Suite to update a ticket in TOPdesk, for example, with fields available through its API, such as category, priority, status and support group. For another application, configure its request and field mapping. The outcome determines the next action: confirm, add information or request review, not merely check whether the request arrived.
Build it yourself: explore the technical approachNeed to publish data or let others submit it? Endpoint Composer exposes a configured Service Automation Suite data object with selected methods and security profiles. Other building blocks handle subsequent processing.
From product to workflow
Slack in your workflow
Pull up a chair. Or join us online.
Over coffee, tea or online: tell us what you are working on.
We can help with the integrations, automation and coordination your process needs, even if your application is not listed yet.
