Never Send to a Broken Destination
Before your newsletter goes out, Notis checks that all your Segment destinations are configured correctly. If something's wrong, you're alerted immediately so you can fix it.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Destination
Tool to retrieve a Destination by ID. Use when you need to fetch the full configuration of a Segment Destination instance by its unique identifier. Falls back US→EU public API and legacy app endpoint; returns minimal envelope on legacy HTML or parse errors.
Why this helps
Sending a newsletter only to discover a destination is misconfigured means lost data and wasted send. Checking destinations manually is another task that gets forgotten.
- Validates in real-time before sends
- Prevents misconfigured destinations from breaking campaigns
- No manual checks needed
- Instant alerts to problems
Setup
Build it in a few focused steps.
- 1Connect Goodbits and Segment to Notis.
- 2Create an automation in the portal or tell Notis conversationally.
- 3Write the prompt: 'Whenever a newsletter is about to be sent from Goodbits, fetch the configuration of each active Segment destination and verify all required settings are present. Alert me immediately if any destination is missing required fields or appears down.'
- 4Set the trigger to 'notis_webhook' to fire right before send.
- 5Choose Slack for instant alerts and test by scheduling a test send and verifying Notis checks destinations before the send completes.
Questions about this workflow
What if a destination check fails? Will the newsletter be blocked?
Notis alerts you but doesn't block sends. You decide whether to proceed or abort based on the alert.
How long does the validation check take?
Usually 10-30 seconds. Notis runs it asynchronously so your send isn't delayed.
Which destinations should I check?
By default, all active destinations. Customize in your prompt to check only critical ones if you prefer.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Goodbits to Segment. A trigger fires from one place; an action lands in another.
Goodbits triggers
Segment actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Labels to Source
Tool to add existing labels to a Source. Use when you have the source ID and want to tag it with metadata labels.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Segment Alias
Tool to alias a previous user ID to a new user ID. Use when merging anonymous and known identities.
Batch Segment Analytics Events
Tool to send multiple analytics calls in a single batch request. Use when you want to reduce HTTP overhead by batching Identify/Track/Page/Screen/Group calls into one request.
Delete Source
Tool to delete a Segment Source. Use when you need to permanently remove a Source by its ID after confirmation.
Get Daily Per Source API Calls Usage
Tool to fetch daily API call counts per source for a given period. Use when you need daily breakdown of API usage by source after determining the reporting period.
Get Destination
Tool to retrieve a Destination by ID. Use when you need to fetch the full configuration of a Segment Destination instance by its unique identifier. Falls back US→EU public API and legacy app endpoint; returns minimal envelope on legacy HTML or parse errors.
Segment Group
Tool to associate an identified user with a group via Segment HTTP Tracking API. Use when grouping users with traits.
Segment Identify
Tool to identify a user and set/update traits via Segment HTTP Tracking API.
Connect any two apps with Notis in the middle.
Goodbits and Segment, 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 Segment.