Give visitor leads a consistent correspondence structure
Turn a newly identified prospect segment into a Spondyr transaction type, so future lead communications have a clear place to start.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Transaction Type
Tool to create a new transaction type. use after defining the json schema for your data to register it in spondyr.
Why this helps
Promising visitor segments can lead to improvised outreach and inconsistent setup across prospect groups.
- Creates a repeatable starting point for correspondence around a qualified visitor segment.
- Reduces the setup decisions needed before a founder can plan follow-up.
Setup
Build it in a few focused steps.
- 1Connect Leadfeeder and Spondyr to Notis once in the portal.
- 2In Automations, choose New Automation and name it for visitor-lead setup.
- 3Write one plain-language prompt asking Notis to create a Spondyr transaction type when a new Leadfeeder prospect segment arrives.
- 4Select an incoming webhook trigger and a channel for run reports.
- 5Send one real segment example through the webhook and check the resulting transaction type.
Questions about this workflow
Does this send an email to the visitor?
No. This workflow creates a Spondyr transaction type; it does not generate or send correspondence.
What starts the automation?
A Notis incoming webhook starts it when an external tool or custom backend submits the prospect-segment event.
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.