Company-Based Workflows in Sparkforge: Triggers and Actions
Company-Based Workflows trigger automations on the Company object and write back to Company fields or associated Contacts — the missing piece for B2B account-level automation.
Company-Based Workflows automate at the account level. They start from Company events (created or updated) and run actions that write directly to Company fields or to the Contacts associated with that Company — closing the gap between contact-level and account-level automation in Sparkforge.
What you can do with them
- B2B onboarding: launch account-level onboarding the moment a Company is created.
- Data sync: keep Company and associated Contact data aligned without manual updates.
- CRM hygiene: clear stale Company fields on status changes for clean reporting.
- Ownership consistency: standardize Account Owner assignment across all related Contacts.
- Pair with Contact workflows: combine Company and Contact flows for end-to-end automation.
Company workflow triggers
| Trigger | Starts when | Filters |
|---|---|---|
| Company Created | A new Company record is added | Owner, tags, fields, or other attributes |
| Company Changed | One or more Company fields are updated | Field/value conditions to react to specific changes |
Company workflow actions
| Action | Available in | Purpose |
|---|---|---|
| Create Company or Associated Contact | Company-based & Contact-based | Create a new Company or add a Contact to an existing Company |
| Update Company or Associated Contact | Company-based & Contact-based | Keep Company data current; optionally sync to associated Contacts |
| Clear Fields of Company or Associated Contact | Company-based & Contact-based | Remove outdated values for clean reporting |
| Create Associated Company | Contact-based only | Create and link a Company from a Contact record |
| Update Associated Company | Contact-based only | Update the Company linked to the current Contact |
| Clear Fields of Associated Company | Contact-based only | Reset selected Company fields from a Contact-based workflow |
Typical use cases
- Auto-launch a B2B onboarding sequence when a Company is created.
- Sync renewal status from Company to all associated Contacts.
- Reset "last activity" Company fields when an account moves to churned.
- Stamp Account Owner across every Contact tied to the Company.
Plan before you build
Map out which fields the trigger should watch and which records the action should write to. Use Association Labels to scope updates to the right Contacts.
Frequently Asked Questions
What's the difference between a Contact-based and Company-based workflow?
Contact-based workflows trigger on Contact events. Company-based workflows trigger on Company events and can update Company fields or associated Contacts.
Can a Company workflow update its associated Contacts?
Yes. Update and Clear Fields actions include an option to apply changes to associated Contacts where available.
How do I keep stale Company data from breaking reports?
Use the Clear Fields action on a Company Changed trigger to reset values when a status changes (e.g. churned, paused).
Can I run Company and Contact workflows together?
Yes. The two workflow types are designed to run side by side for end-to-end B2B automation.
Which trigger should I use for field updates?
Use Company Changed and add field/value conditions so the workflow only fires for the specific updates that matter.
Was this article helpful?
Thanks for the feedback.