Add owner context to ClickHouse signal reviews
Make it easier to decide who should follow up by bringing available Salesforce owner details into the review.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get user info
Retrieves information about the current user or a specific user in salesforce.
Why this helps
A useful finding can lose momentum when the person responsible for its CRM record is unclear.
- Show available user context for relevant CRM records.
- Make follow-up responsibility easier to review.
- Avoid manually looking up CRM owners after an analytics check.
Setup
Build it in a few focused steps.
- 1Connect ClickHouse and Salesforce once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis to create it from any channel.
- 3Describe the outcome: query ClickHouse for the stated findings, identify their Salesforce record owners using available IDs, retrieve relevant Salesforce user details, and summarize owner context for review.
- 4Choose a recurring schedule, then select where run reports should go.
- 5Test with one real finding and confirm the owner details correspond to the Salesforce record.
Questions about this workflow
Does this reassign Salesforce records?
No. It retrieves user information and summarizes owner context.
What information is needed to identify an owner?
Provide the Salesforce user ID or the owner identifier present on the relevant Salesforce record.
What if no owner is available?
Have Notis report that owner details could not be resolved so the team can decide on the next step.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link ClickHouse to Salesforce. A trigger fires from one place; an action lands in another.
ClickHouse 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.
ClickHouse 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.