Deliver prepared prospect correspondence after approval
Once your process marks a previously generated item ready, use a webhook to trigger its Spondyr delivery and avoid a forgotten handoff.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Deliver Spondyr correspondence
Tool to trigger delivery of a previously generated correspondence. use after calling the generate api.
Why this helps
A prepared follow-up can sit untouched when the final delivery step gets lost among other founder tasks.
- Automates the handoff for correspondence already generated elsewhere in the process.
- Connects an explicit ready signal with Spondyr's delivery action.
Setup
Build it in a few focused steps.
- 1Connect Leadfeeder and Spondyr to Notis once in the portal.
- 2Create a new automation named approved prospect correspondence delivery.
- 3Write one plain-language prompt telling Notis to deliver only the previously generated Spondyr correspondence identified by an approved ready event.
- 4Choose an incoming webhook trigger and a channel for run reports.
- 5Test with one approved real example and verify its delivery status in Spondyr.
Questions about this workflow
Does this generate the email first?
No. The action delivers previously generated correspondence; generation must happen in a separate process.
Should every Leadfeeder visitor signal trigger delivery?
No. Use an explicit approval or ready event from your process before triggering delivery.
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.