Send Notification
The Send Notification action tells people on your side when something happens to a contact: a form is submitted, a contact qualifies for a Workflow step, a lead crosses a score threshold. It's the sales alert, the "a hot lead just raised their hand" email, without anyone watching a dashboard.
Notifications go to your team, not to the contact. To email the contact, use Send Email. To post to a Slack channel instead, use Send Slack Notification.
Recipients
Add as many recipients as you need, in any combination. Each new Send Notification action starts with you as its first recipient.
Paminga Users
Pick any user in your account. Choose how each one hears about it: Email, In-App (the Notification Center in Paminga), or both. In a Workflow, notifications go by email only.
Lead Owner
Check Send to Lead Owner via Email and the notification goes to whoever owns the contact. You don't need one action per sales rep, and the right person is notified even as ownership changes.
In a Workflow, many contacts can qualify for a step at once. With a custom message, each Lead Owner gets one email listing only the contacts they own, not the whole group. A contact with no owner doesn't generate an owner email. If a Lead Owner is also listed as a recipient in their own right, they get the whole group in a single email instead of two. Only the contact list is per owner: tokens in the Custom Subject and Custom Message fill from the first contact in the group, for every recipient. With a Paminga Email, there is no per-owner list: each Lead Owner, like every other recipient, gets that Email once.
Persons Without a Paminga Account
Add any Email Address: a shared sales inbox, a partner, a manager who doesn't log in to Paminga.
Notification Content
Under Send, choose what the notification says.
A Custom Message
Write a Custom Subject and a Custom Message. Both accept personalization tokens, so "New demo request from" followed by the contact's name and company is one token away. The message editor handles formatting and links.
A Paminga Email
Choose a published Email from Email to Send and the notification uses that Email's own subject line and content. Click the eye icon beside it to preview what recipients will get. This is the way to send a polished, on-brand internal alert, or one you reuse across several actions and want to edit in one place.
Personalization in the Email fills from the contact who triggered the notification. When one Workflow notification covers several contacts, it fills from the first of them.
A few things are different from a normal send, on purpose:
- The Email must have a published version. Paminga sends the published version, not your draft.
- Notification sends are never counted in Email statistics, Contact activity, or reports. Your team opening an alert shouldn't inflate an Email's open rate.
How Often Recipients Hear From It
Outside a Workflow (a form submission, for example), the action runs for each contact it's triggered for, but a recipient gets at most one email each time the action runs. When one run covers several contacts, a recipient already emailed for an earlier contact in that run isn't emailed again.
In a Workflow, everyone who qualifies for the step together is covered by one notification per recipient. A step that qualifies 200 contacts sends each recipient one email, not 200.


