Operational Workflows
Not every automation talks to a contact. Plenty of them are pure back-office machinery: assigning lead owners, normalizing field values, pushing records into your CRM, tidying up data after an import. They run constantly, they touch a lot of people, and they never send a thing.
Paminga lets you say so. Mark an automation as operational and it stops counting as somewhere a contact "is" — which matters the moment you want a different automation to refuse anyone who is already in the middle of a campaign.
Marking an Automation as Operational
In an automation's Settings step, check This is an Operational Workflow.
That flag does one thing, and it is worth being precise about it: an operational automation no longer blocks entry anywhere else. It does not change how the automation itself runs, who it qualifies, or what its actions do. It is a classification, not a behavior.
Reach for it when the automation sends nothing. If it emails, texts, or otherwise reaches the contact, it is not operational — whatever else it does alongside.
Requiring Exclusive Entry
The companion setting is Only add Contacts who are not currently in another Non-Operational Workflow.
Check it and the automation refuses anyone who is currently active in another automation — unless that other automation is operational, in which case it is ignored. A contact sitting in "Assign Lead Owner" is not being talked to, so it would be strange to lock them out of your webinar follow-up on that basis.
This is how you stop someone receiving two streams of email at once. A contact halfway through an onboarding nurture will not be pulled into a product-launch campaign until they finish.
The two settings are mutually exclusive by design. An operational automation sends nothing, so there is no double-messaging for it to prevent — checking This is an Operational Workflow hides the exclusive-entry option.
It Gates Entry, Not Participation
Switching exclusive entry on affects who can join from that point forward. Contacts already in the automation stay exactly where they are and keep running through it. Nobody is removed, and nothing is re-evaluated retroactively.
The same goes the other way. A contact who is refused entry today is not queued up or remembered — they are simply not added. If they finish their other automation and still match your audience, the next evaluation will take them.
Where the Rule Applies
Exclusive entry is honored wherever a contact would normally be added:
- Audience evaluation — contacts matched by the automation's audience
- Manual adds — adding a contact from their record
- Add to Automation actions — fired by another automation
- The API
When you add a contact by hand and the automation refuses them, Paminga tells you which automation is holding them, so you are never left guessing why nothing happened.
Abandoned cart automations are the exception. They route contacts directly from a cart event, and that path does not consult the setting.
Audience evaluation runs continuously and at scale, which means it works from data that can be a moment behind. In rare cases a contact who joined another automation seconds earlier may still be admitted. Manual adds and actions are checked at the moment they happen and are not subject to this.
Requalification Still Applies
Exclusive entry sits on top of your requalification rules rather than replacing them.
If a contact has finished this automation and is eligible to come back through it, they are still refused while they are active somewhere else. Both conditions have to be satisfied: your requalification rules must allow re-entry, and the contact must not be held by another non-operational automation.
A Worked Example
Say you have three automations:
| Automation | Operational? | Exclusive entry? |
|---|---|---|
| Lead Owner Assignment | Yes | — |
| Onboarding Nurture | No | No |
| Webinar Follow-Up | No | Yes |
- A contact in Lead Owner Assignment can enter Webinar Follow-Up. The operational automation is ignored.
- A contact in Onboarding Nurture cannot, until they finish. That is the point.
- A contact in neither enters normally.
- A contact in both Lead Owner Assignment and Onboarding Nurture is refused — the nurture is what blocks them, not the operational automation.
