Measure address validation outcomes in Gleap
A webhook from your backend can prompt Notis to report address validation outcomes to Gleap as server-side customer events.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Track events
Tool to track server-side customer events. Use when you have collected a batch of events and want to send them to Gleap via the /admin/track endpoint.
Why this helps
Without consistent events, it is hard to see whether address validation is helping customers complete important flows.
- Make validation outcomes available for product analysis in Gleap.
- Compare successful and unsuccessful address attempts over time.
- Avoid manually assembling validation counts from operational logs.
Setup
Build it in a few focused steps.
- 1Connect Google address validation and Gleap to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to send a Gleap event when your backend reports an address validation result.
- 3Describe the event and context in one plain-language instruction.
- 4Choose an incoming webhook trigger, select a channel for run reports, and test with one successful and one failed result.
Questions about this workflow
Where does the trigger come from?
Your backend sends an incoming webhook to Notis after it receives a Google address validation result.
Can the event include customer context?
Yes. Tell Notis which relevant customer and flow context from the webhook to include in the Gleap event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google address validation to Gleap. A trigger fires from one place; an action lands in another.
Google address validation triggers
Gleap actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive a Ticket
Tool to archive a ticket. Use after confirming the ticket ID and that the ticket is resolved. Call when moving tickets to history.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a Collection
Tool to create a help center collection. Use when adding a new organizational grouping in your Help Center.
Create a new chat message
Tool to create a new chat message. Use when sending a message in an active chat session.
Create a new team
Tool to create a new team. Use when you have team details ready and want to assign tickets among members.
Create a new ticket
Tool to create a new ticket. Use when you have ticket details ready to open a support ticket.
Delete a User from a Project
Tool to remove a user from a project. Use when you need to revoke a user's access by their ID.
Get a Checklist
Tool to retrieve a specific engagement checklist by its ID. Use after obtaining a valid checklistId.
Get a Collection
Tool to retrieve a help center collection by ID. Use when you need to fetch specific collection details by its ID.
Connect any two apps with Notis in the middle.
Google address validation and Gleap, 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 Gleap.