Catch recipient setup gaps before planning follow-up
Review configured recipients on a regular cadence so prospect correspondence planning does not stall on an avoidable setup question.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Recipients
Tool to list all recipients for a transaction type. use when you need to discover or verify all configured recipients before sending or managing correspondence.
Why this helps
Recipient configuration can be easy to forget until the moment a founder is ready to prepare a message.
- Surfaces the current recipient configuration for selected prospect-related transaction types.
- Makes recipient readiness a predictable review instead of a last-minute interruption.
Setup
Build it in a few focused steps.
- 1Connect Leadfeeder and Spondyr to Notis once in the portal.
- 2Create an automation called recipient readiness check.
- 3Write one plain-language prompt asking Notis to list recipients for the Spondyr transaction types used with Leadfeeder prospects.
- 4Select a recurring schedule and your preferred channel for run reports.
- 5Review one run and verify that the listed recipients are the ones you expect.
Questions about this workflow
Will this add recipients if any are missing?
No. It lists configured recipients so you can see the current setup.
Does it need a Leadfeeder webhook?
No. This is a scheduled Spondyr configuration check informed by your lead workflow.
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.