Cross-Object Workflow Actions in Sparkforge: Add, Remove, Find

By Sparkforge Support Team ·Last reviewed May 3, 2026

Sparkforge's cross-object workflow actions add, remove, or find associated Contacts, Companies, or Custom Objects — so automations follow the relationships between records, not just the record that triggered the workflow.

Sparkforge Workflows support actions that understand relationships between records (associations). Instead of acting only on the record that triggered the workflow, you can target associated Contacts, Companies, or Custom Objects — and find records using IDs, external IDs, or field criteria.

Why it matters

Deeper automation: build flows that act across Contacts, Companies, and Custom Objects without manual steps.
Relationship targeting: filter by Association Label to reach exactly the right related records.
Precise lookup: match via Record ID, External ID, or field filters — including dynamic webhook values.
Branching logic: split on Record Found vs. Record Not Found and choose Earliest, Latest, or All when multiple records match.
Operational control: add or remove associated records from other workflows to start or stop processes at the right moment.

Add Associated Records to Workflow

Use this action when the current record should enroll its related records (Contacts, Companies, or Custom Objects) into another workflow.

Select the associated Object Type (Contact, Company, or a Custom Object).
Filter recipients by Association Label (e.g., Buyer, Account Owner, Assigned Dealer).
Pick the target workflow.

Example: when a Car (Custom Object) is updated to Ready for Sale, automatically add all its associated Dealers to the Dealer Notification Workflow.

Remove Associated Records from Workflow

Use this to unenroll associated records from a different workflow when conditions change — for example when a deal closes or a property sells.

Target Contacts, Companies, or Custom Objects via associations.
Filter by a specific Association Label so you remove only the right relationships.
Specify which workflow to remove them from.

Example: when a Property record is marked Sold, remove its associated Buyers from the Active Listings Workflow to stop further notifications.

Find Object Record / Find Company

Use Find to locate an existing record. Match via Record ID, External ID, or field filters, and pass dynamic values from an Inbound Webhook.

Match via Record ID, External ID, or field-based filters.
Use webhook variables (e.g. {{inboundWebhookRequest.body.subscription_ref}}).
Choose how to handle multiple matches: Earliest, Latest, or All.
Branch on Record Found vs. Record Not Found.

Example: when a webhook posts { "companyDomain": "acme.com" }, find the matching Company record and enroll it in a workflow.

Frequently Asked Questions

What's the difference between Add to Workflow and Add Associated Records to Workflow?

Add to Workflow enrolls the current record. Add Associated Records to Workflow enrolls other records linked to the current record via associations, filtered by an Association Label.

Can I target more than one Association Label in a single action?

No. One label per action. Add another Add or Remove Associated Records action for each additional label.

How do Earliest, Latest, and All affect the Find result?

Earliest or Latest proceed with a single best match. All applies the downstream path to every matching record.

Can Find use values from an inbound webhook?

Yes. Reference webhook fields directly (for example {{inboundWebhookRequest.body.subscription_ref}}) inside the Find filter.

What happens when Find returns no record?

The workflow takes the Record Not Found branch, so you can handle missing records separately from matches.