Keep high-intent segment rules ready
When a visitor segment meets your chosen intent threshold, add the corresponding condition rule to its Spondyr transaction type.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Condition
Tool to create a new condition. use when defining detailed rules for template selection based on transaction data.
Why this helps
Remembering to update correspondence rules after prospect patterns change adds one more operational task to an already busy day.
- Keeps a segment-specific condition rule aligned with a reported intent change.
- Turns a manual configuration reminder into a clear webhook-driven task.
Setup
Build it in a few focused steps.
- 1Connect Leadfeeder and Spondyr in Notis once through the portal.
- 2Create a new automation and name it for high-intent segment rules.
- 3Describe in one plain-language prompt which Leadfeeder segment event should lead Notis to create a Spondyr condition for the relevant transaction type.
- 4Choose an incoming webhook trigger and select where Notis should report runs.
- 5Test with one real high-intent segment event and review the condition created in Spondyr.
Questions about this workflow
Does Leadfeeder provide the automation trigger here?
No. Leadfeeder has no available integration trigger events in this package; a Notis incoming webhook starts the workflow.
Can the condition directly send outreach?
No. The action creates a Spondyr condition. Sending correspondence requires a separate supported process.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Leadfeeder to Spondyr. A trigger fires from one place; an action lands in another.
Leadfeeder triggers
Spondyr actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Conditions
Tool to list all conditions for a transaction type. use when you need to retrieve all condition rules defined for a specific transaction type.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Condition
Tool to create a new condition. use when defining detailed rules for template selection based on transaction data.
Create Transaction Type
Tool to create a new transaction type. use after defining the json schema for your data to register it in spondyr.
Deliver Spondyr correspondence
Tool to trigger delivery of a previously generated correspondence. use after calling the generate api.
Update Event Type
Tool to update an existing event type. use when you need to modify the name or associated transaction type of an event type. example: rename the 'ordershipped' event to 'orderdelivered'.
List Event Types
Tool to list all event types for a given transaction type. use when you need to discover available events after retrieving transaction types.
Get Spondyr Status
Tool to retrieve the status of a previously generated correspondence. use after generating correspondence to check its processing and delivery status.
Get Transaction Types
Tool to retrieve a list of available transaction types. use after authentication to discover data schemas.
Connect any two apps with Notis in the middle.
Leadfeeder and Spondyr, 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 Spondyr.