Keep correspondence structure in step with prospect data
When your approved prospect data structure changes, update the related Spondyr transaction type so future correspondence planning stays coherent.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Transaction Type
Tool to update an existing transaction type. use after retrieving a transaction type to apply changes. example: "update transaction type 'order' with new json schema."
Why this helps
Schema changes can be easy to defer, creating uncertainty about which structure a prospect workflow expects.
- Routes an approved structure update to the relevant Spondyr transaction type.
- Makes schema maintenance easier to tie to a clear change signal.
Setup
Build it in a few focused steps.
- 1Connect Leadfeeder and Spondyr to Notis once in the portal.
- 2Create a new automation named for prospect schema updates.
- 3Write one plain-language prompt asking Notis to update the specified Spondyr transaction type when an approved Leadfeeder prospect-data change arrives.
- 4Select an incoming webhook trigger and choose where run reports should appear.
- 5Test with one approved example and inspect the updated transaction type in Spondyr.
Questions about this workflow
Does this invent a schema from visitor data?
No. The prompt should direct Notis to apply an approved schema change supplied by your process.
Can I use this for every visitor update?
Use it for meaningful, approved structure changes rather than routine visitor activity.
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.