Keep event names aligned with your prospect language
When your prospect-stage vocabulary changes, update the related Spondyr event name so future workflow reviews stay clear.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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'.
Why this helps
Old event labels linger after process changes and force founders to mentally translate between current and outdated terms.
- Keeps an existing event label aligned with the current prospect-stage vocabulary.
- Reduces small translation decisions during later correspondence reviews.
Setup
Build it in a few focused steps.
- 1Connect Leadfeeder and Spondyr to Notis once in the portal.
- 2Create an automation named for prospect-stage event naming.
- 3Write one plain-language prompt asking Notis to update the corresponding Spondyr event type name when the webhook reports an approved stage-label change.
- 4Select an incoming webhook trigger and choose a run-report channel.
- 5Test with one real approved rename event and confirm the event type name in Spondyr.
Questions about this workflow
Will this create a new event type?
No. It updates an existing event type name.
Should every label change trigger an update?
Use the prompt to limit updates to approved naming changes reported by your external tool or backend.
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.