Know who a prospect workflow is configured to reach
When an important visitor signal arrives, retrieve the configured recipient before you plan the next correspondence step.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Recipient
Tool to retrieve details of a specific recipient. use when you need to fetch recipient configuration for a given transaction type. example: "retrieve recipient 'customer' for transaction type 'orderplaced'."
Why this helps
An urgent prospect signal can trigger a scramble to confirm who an existing communication setup is aimed at.
- Puts recipient configuration in view when a priority prospect signal arrives.
- Reduces the need to switch tools and search for setup details by hand.
Setup
Build it in a few focused steps.
- 1Connect Leadfeeder and Spondyr to Notis once in the portal.
- 2Create a new automation and name it for priority prospect recipient checks.
- 3In one plain-language prompt, tell Notis to retrieve the relevant Spondyr recipient when the webhook reports a priority Leadfeeder prospect.
- 4Choose an incoming webhook trigger and a channel for run reports.
- 5Test with one real priority event and confirm the recipient details match Spondyr.
Questions about this workflow
Does retrieving a recipient send a message?
No. The action retrieves recipient configuration for review.
How does Notis learn about the priority signal?
An external tool or custom backend sends the event to the Notis incoming webhook.
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.