Update Amplitude user properties after Addresszen location verification
Keep user location properties in step with verified Addresszen results, using the identity and details your backend includes in a webhook.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update User Properties in Amplitude
Update user properties without sending an event.
Why this helps
Manually keeping user location attributes current can create stale analytics and extra follow-up work.
- Update user properties after a backend reports a verified location.
- Use the Amplitude identity and location attributes supplied in the request.
- Avoid repetitive manual updates to user analytics profiles.
Setup
Build it in a few focused steps.
- 1Connect Addresszen and Amplitude once in the Notis portal.
- 2Create an automation in the portal or tell Notis what outcome you want from any channel.
- 3Ask Notis to update Amplitude user properties when a webhook reports a verified Addresszen location, using only the identity and properties included in the request.
- 4Choose the webhook trigger and select where Notis should send run reports.
- 5Test with one real verification result and check the intended Amplitude user.
Questions about this workflow
What user identity does this need?
The webhook request must include the Amplitude identity information needed for the update. The workflow cannot infer a user identity from an address alone.
Does Addresszen provide this webhook automatically?
No Addresszen trigger event is listed. Your connected backend or another system must send the verification result to the Notis webhook.
Can this update any location data I choose?
It can use properties included in the webhook request. Decide which verified location details are appropriate to send and include them in that request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Addresszen to Amplitude. A trigger fires from one place; an action lands in another.
Addresszen triggers
Amplitude actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Amplitude Cohort Status
Check whether a cohort export is in progress or ready to download.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Bulk Assign Annotations to Category
Assign multiple annotations to a category in bulk.
Create Amplitude Event Category
Create a category to organize events.
Cancel User Deletion
Cancel a pending user deletion request while the job is still in staging.
Create Amplitude Event Type
Create a trackable event type.
Delete Amplitude Event Category
Permanently delete an event category.
Create Chart Annotation in Amplitude
Add an annotation to an analytics chart to mark an important date.
Delete Amplitude Event Type
Delete an event type; live events are marked as deleted.
Connect any two apps with Notis in the middle.
Addresszen and Amplitude, 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 Amplitude.