Your Design System Address Components Should Teach Best Practices
When designers update address input field components in your Zeplin library, Notis validates the placeholder addresses. Examples are always real and correctly formatted.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Validate Address
Tool to validate and standardize addresses. Use when you need detailed parsing, geocode, and deliverability verdict of an address.
Why this helps
Design systems document component patterns including placeholder text. Bad or outdated addresses in component examples teach designers wrong patterns. These spread across products.
- Design system examples are always accurate
- Designers learn correct patterns
- Consistency across all products
Setup
Build it in a few focused steps.
- 1Connect Zeplin and Google Address Validation to Notis.
- 2Ask Notis: "When an address input component in our design system library is updated, validate the placeholder addresses to ensure they're correct and realistic."
- 3Trigger via Zeplin component update webhook.
- 4Send validation results to your design systems Slack channel.
- 5Update a component in the library and verify the placeholder is validated.
Questions about this workflow
What if I want to use a test address that's not real?
You can exclude that component or field from validation. Notis will validate the others.
Do component examples need to be different for each region?
Yes. You can set up regional variants of the component with localized example addresses.
How often should I validate component examples?
Whenever you update a component. Notis can also run weekly checks to catch any drift.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Zeplin to Google address validation. A trigger fires from one place; an action lands in another.
Zeplin triggers
Google address validation actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Provide Validation Feedback
Tool to provide feedback on an address validation attempt. Use after completing an address validation sequence.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Validate Address
Tool to validate and standardize addresses. Use when you need detailed parsing, geocode, and deliverability verdict of an address.
Connect any two apps with Notis in the middle.
Zeplin and Google address validation, 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 Google address validation.