Keep account teams informed about transaction status changes
Record the status update where account teams already look for customer context, using the details supplied in the webhook.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create note
Creates a new note attached to a salesforce record with the specified title and content.
Why this helps
Transaction changes can reach operations without making it into the account history used by customer-facing teams.
- Add transaction context to the identified Salesforce account.
- Give account teams a durable reference for the reported status.
- Avoid guessing account ownership when the match is unclear.
Setup
Build it in a few focused steps.
- 1Connect Blocknative and Salesforce once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis to create an account note containing the reported transaction status and details when a valid account identifier is included.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real status-change request and a known account.
Questions about this workflow
What if the request does not include an account identifier?
The workflow should not guess. It can report that the note could not be attached until a valid account is identified.
Can the note summarize prior status changes?
Only if the request or available Blocknative data contains that history. Otherwise it records the supplied update.
Does the workflow change the Salesforce account fields?
No. It creates a note attached to the account.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blocknative to Salesforce. A trigger fires from one place; an action lands in another.
Blocknative triggers
Salesforce actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Salesforce Account
Deprecated: creates a new salesforce account using a json post request, requiring 'name'; specific fields (e.g., custom, dunsnumber) may have org-level prerequisites.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add contact to campaign
Adds a contact to a campaign by creating a campaignmember record, allowing you to track campaign engagement.
Add lead to campaign
Adds a lead to a campaign by creating a campaignmember record, allowing you to track campaign engagement.
Add product to opportunity
Adds a product (line item) to an opportunity. the product must exist in a pricebook entry that's associated with the opportunity's pricebook.
Apply lead assignment rules
Applies configured lead assignment rules to a specific lead, automatically routing it to the appropriate owner based on your organization's rules.
Associate contact to account
Associates a contact with an account by updating the contact's accountid field.
Clone opportunity with products
Clones an opportunity and optionally its products (line items). creates a new opportunity with the same field values and products as the original.
Clone record
Creates a copy of an existing salesforce record by reading its data, removing system fields, and creating a new record. optionally apply field updates to the clone.
Connect any two apps with Notis in the middle.
Blocknative and Salesforce, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Salesforce.