Feedback → product team
Connect relevant customer feedback to product ideas and agreed follow-up.
All integrations
Customer & work data
Aha!
Connect ideas and features to service requests. Share relevant progress with the customer-facing team.
From product to process
How to use the integration
Keep customer records aligned
Share agreed customer and contact details with service or accounting applications.
Ticket → issue
Link the service request to a development issue and return agreed progress updates.
Combine into one controlled process
Data → rules → execution-
Combine
Customer or issue + service request + rules
-
Determine & check
Combine data and determine the next action
-
Execute & report back
Start onboarding or a work task · Notify team · Return outcome
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
Data transferred.
But is the work complete?
Service Automation Suite connects Aha! 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
Aha!
For example. Also with other teams, suppliers and applications.
Verify. Inform. Report.
What is complete? Who needs to act? Which exception needs attention?
From AFAS to other apps
Put your AFAS data to work across your applications.
Re-entering contacts and companies in every application? Use AFAS as the source and share the data the other system needs. Beyond TOPdesk, Aha! is one example: we keep a customer’s contacts and companies current there using AFAS data.
For another application, we configure the available API, record matching and field mapping.
Match relationships & map fields
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
Contacts & companies
Aha!Update contacts & companies
Choose which data to share
Determine which companies and contacts the destination needs and which fields AFAS owns. Share only agreed data and preserve the relationship between person and company.
Match the same relationship across systems
A different name or number need not mean a new relationship. Service Automation Suite uses configured identifiers and a shared mapping table. Reuse that matching in another integration, for example with TOPdesk. If a reliable match is missing, apply the agreed review process.
Update selectively and handle differences
In the Aha! example, agreed contact and company data is updated from AFAS. Configure what happens for a new relationship, a change, an inactive record or an API rejection. This avoids duplicate entry and assigns ownership to discrepancies.
Writing back to AFAS is a separately configured route, not automatic two-way synchronisation.
Customers & suppliers
Your own systems. Shared progress.
Collaboration Composer connects customer, team and supplier service environments. No separate emails to discover who picked up a ticket.
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.
Aha!Relevant data or workflow status
Update, execute and record outcomes
Share the relevant ticket
Define the ticket and context the other party needs. Keep unshared information in its own environment.
Connect progress
Align agreed fields, comments and statuses.
Track resolution
Return updates to the original request and surface missing feedback.
Under the hood
How to connect, test and manage the integration.
For administrators who want to understand how it works: connect Aha! 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
Synchronise data and return the outcome
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.
- Source ID and external reference
- Retain verified relationships between records and reuse them across integrations.
- Fields, codes and required data
- Select the required data, translate values and enrich from shared tables. Route uncertain matches for review.
- Result reference and processing status
- Use the available response for feedback and agreed follow-up actions.
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.
Time recorded, but not yet accounted for.
Service work is complete but time entries do not match a known customer, project code or agreed processing route.
- Combine
- Combine time entries with central customer and project relationships and accounting rules. Request specific missing information.
- The outcome determines what follows
- Accepted: retain the accounting reference. Rejected: have the owner correct the cause. Resending an entry requires checking whether it was already processed.
- The benefit
- Less investigation and correction between service and finance without automatically treating errors as billable work.
A different name does not mean a new record.
A person or organisation has a different name in the source than at a customer or supplier. Matching text again can create incorrect or duplicate relationships.
- Combine
- Retain verified identifiers and source rules in a shared table. Reuse the relationship for requests, tickets and other integrations.
- The outcome determines what follows
- Known key: use the relationship. Multiple candidates or a missing identifier: request review. Once confirmed, reuse the established relationship.
- The benefit
- A consistent data foundation managed by your team instead of investigated again for every connection.
Refreshing a report does not guarantee reliable data.
A source request can succeed while data is missing, differently coded or not yet fully retrieved.
- Combine
- Combine pagination and output mapping with agreed data checks. Use shared relationship tables to connect sources.
- The outcome determines what follows
- Checks passed: prepare the dataset. Deviation: request review and expose freshness. Temporary API failures follow a bounded recovery path.
- The benefit
- A clearer distinction between a technically successful import and information fit for decision-making.
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
Aha! 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.
