Alert on Change Events with Flow
Build a record-triggered Flow on Proff Change Event to notify users of company changes.
You can get notified when important company updates appear in Proff — for example approved annual accounts, mergers, or bankruptcy notices.
Proff Connect stores these updates as Proff Change Event records. You can build a Salesforce Flow that watches for new events and runs the automation you need.
Change Events are created by Real-Time Changes. A Change Job must be active for your country before alerts will work.
Important
Create a record-triggered Flow on the Proff Change Event object, set to run when a record is created.
Do not build the Flow on Account. The Account is already linked on the Change Event via Related Account.
How a Change Event looks
When an announcement arrives, the record typically includes:
| Field | Example | What it means |
|---|---|---|
| Related Object | Announcements | The type of change |
| New Value | ARSO — Godkjente årsregnskap (24.06.2026) | The code, then a short description |
| Related Account | The matching company in Salesforce | Who the alert is about |
The code is the first part of New Value (before —), for example ARSO, FUSJ, or WAAP.
See the full list: Announcement codes.
Note
This Flow runs once per Change Event. If many Accounts get the same type of announcement on the same day, users may receive one notification per Account. That is expected. If you prefer one combined email instead, see Option B — One combined email below.
What you can do in the Flow
Once the Flow finds a matching Change Event, you can use the same kinds of actions as in any other Salesforce Flow. Examples:
- Send a push / in-app notification or email to the Account Owner
- Notify Opportunity owners (or other related users) linked to that Account
- Create a Task or Case for follow-up
- Update fields on the Account or related records
- Trigger further logic — for example call another Flow, start an approval, or kick off an integration
In practice you have the same automation possibilities as with other Salesforce Flows. Choose the actions that fit your process.
Option A — Notify as soon as a change appears
Use this when someone should be alerted right away (for example bankruptcy or merger).
STEP 1 — Create the Flow
- Go to Setup.
- Search for Flows and open it.
- Click New Flow.
- Choose Record-Triggered Flow.
- Set:
- Object: Proff Change Event
- Trigger: A record is created
- Optimize for: Actions and Related Records
STEP 2 — Set when the Flow should run (entry criteria)
You want announcement events that start with a specific code.
Example: alert on ARSO (approved annual accounts)
| # | Field | Operator | Value |
|---|---|---|---|
| 1 | Related Object | Equals | Announcements |
| 2 | New Value | Starts With | ARSO |
Set Condition Requirements to All Conditions Are Met (AND) — both must be true.
Always use Starts With for the code (not Equals or Contains). New Value is a full sentence that starts with the code.
Several codes in the same Flow
Add more New Value rows, then switch to Custom Condition Logic.
Example: ARSO, FUSJ, or WAAP
| # | Field | Operator | Value |
|---|---|---|---|
| 1 | Related Object | Equals | Announcements |
| 2 | New Value | Starts With | ARSO |
| 3 | New Value | Starts With | FUSJ |
| 4 | New Value | Starts With | WAAP |
Custom logic: 1 AND (2 OR 3 OR 4)
That means: Related Object is Announcements, and New Value starts with one of the codes.
Important
Do not filter only on Sync Status = Needs Review. Too many different changes use that status, so you would get too many alerts.
STEP 3 — Add your actions
After the start element, add the actions you need — for example:
| What you want | Typical Flow action |
|---|---|
| Notification in Salesforce (the bell) | Send Custom Notification |
| Email to Account Owner (or others) | Send Email / Email Alert |
| Follow-up on the Account | Create Records → Task |
| Further automation | Subflow, field updates, or other Flow elements |
Before using the bell: create a Custom Notification Type in Setup (Notification Builder → Custom Notifications), then select it in the Flow.
Useful details to include in a message:
- Related Account name
- Organisation number (Company Identifier)
- New Value (the full text with code and description)
Save the Flow, then click Activate.
Option B — One combined email (scheduled Flow)
Use this if you do not want a separate alert for every Account, but prefer a daily or weekly summary.
- Create a Schedule-Triggered Flow (not record-triggered).
- Set it to run daily or weekly.
- In the Flow, get recent Proff Change Event records (for example created since the last run, Related Object = Announcements, and New Value starting with the codes you care about).
- Build a short summary (list of Accounts and what changed).
- Send one email with that summary.
This takes a bit more Flow setup, but avoids many individual notifications when many companies change at once.
Optional — Status changes (for example bankruptcy text)
Some critical updates arrive as status changes, not as announcement codes. For those, use a separate record-triggered Flow (or separate conditions) with Path /status and New Value that contains words like konkurs.
Announcement codes alone do not cover every bankruptcy-related update. See also codes such as WAAP under Announcements in the codes list.
Quick picks
| Need | Related Object | New Value Starts With |
|---|---|---|
| Annual accounts | Announcements | ARSO |
| Merger | Announcements | FUSJ |
| Bankruptcy opening | Announcements | WAAP |
| Deletion | Announcements | SLET |
Full list: Announcement codes.
Field names (if you use API names)
In Flow Builder you usually see field labels. In formulas or SOQL, managed package fields may look like this:
| Label | API name |
|---|---|
| Related Object | A82__Related_Object__c |
| New Value | A82__New_Value__c |
| Related Account | A82__Related_Account__c |
| Company Identifier | A82__Company_Identifier__c |
Was this article helpful?