A conflict is a relationship nobody remembered
Conflict checks fail when the relevant relationship involves a person who is not in the room, for example a supplier who is also a customer, a candidate who has worked for a competitor, or an adviser who sits on two boards.
A growing business cannot afford to check every system by hand for every new engagement, so the check becomes a question raised in a meeting and answered from memory.
A name-based check fails for corporate structure. If a subsidiary has a different name, the two are part of the same group, and a relationship with one is a relationship with the other.
Whether an overlap is a conflict is not straightforward. It depends on the type of engagement, the information at issue, and, in some cases, professional rules. Because of that, a person concludes.
How the ActionFlow runs on the canvas
The engagement starts at a Start node, with the counterparty, the nature of the work, and the people concerned.
Several searches run in parallel. A Salesforce or HubSpot node checks customers and suppliers. A PostgreSQL node checks contracts. An Airtable node checks declared interests. An HTTP Request node checks anything else your inventory names.
The HTTP Request node can also resolve corporate structures when you have subscribed to a source for it, because that is how the subsidiary case is caught rather than by name matching.
A Merge node assembles the results. The Generate Object node then goes through them. It produces candidate overlaps, including the identified relationship, where it was found, and an explanation of why it might be important, presented as a question rather than a conclusion.
The Filter node logs matches it considers coincidental rather than removing them.
A Notion node records each overlap and each search performed, because the conflict-check record must show what was examined, not only what was found.
The Slack node sends it to the person responsible for assessing it. The flow does not clear anything or block anything.
Nodes this ActionFlow uses
- Start: takes the counterparty, the nature of the work, and the people involved.
- Salesforce (Integration): checks customer and supplier relationships. HubSpot fits the same slot.
- PostgreSQL (Data): checks contracts. Airtable holds declared interests.
- HTTP Request (Util): resolves corporate structure so subsidiaries are not missed.
- Merge (Control): assembles every search before anything is judged.
- Generate Object (AI Core): returns overlaps phrased as questions, with where each was found.
- Notion (Integration): records what was searched as well as what was found.
- Slack (Communication): delivers the check to the person who assesses it.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.