Know which indexed fields can support profile follow-up
A changed subscriber profile may call for a different lookup. Get the Elasticsearch mapping in the run report so you can see which fields are available before searching.
Trigger
Profile Update Trigger
Fires when a subscriber’s profile is updated.
Action
Get Index Schema
View the structure and field mappings of an index.
Why this helps
Teams may not know whether an Elasticsearch index contains the fields needed to investigate an updated subscriber profile.
- Surface the selected index's field names and types after a profile update.
- Make it easier to decide whether an existing index can support a follow-up search.
- Avoid guessing about index structure.
Setup
Build it in a few focused steps.
- 1Connect Mailchimp and Elasticsearch once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3In one instruction, ask Notis to retrieve the schema for the relevant Elasticsearch index after a subscriber profile update and summarize fields useful for a follow-up lookup.
- 4Choose the Mailchimp Profile Update trigger and select where run reports should go.
- 5Test with one real profile update and review the mapping summary.
Questions about this workflow
Does this inspect the updated subscriber's document?
No. This automation retrieves the schema of a specific index. It does not retrieve a subscriber document or change the mapping.
How does Notis know which index to inspect?
Name the relevant index in the instruction. If you do not know its name, use an index-list workflow or first check the cluster's available indices.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Mailchimp to Elasticsearch. A trigger fires from one place; an action lands in another.
Mailchimp triggers
Elasticsearch actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Index Schema
View the structure and field mappings of an index.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Indices
Lists available Elasticsearch indices.
Campaign Trigger
Fires when a campaign is sent or has an event.
Query Index
Searches an Elasticsearch index for documents.
Profile Update Trigger
Fires when a subscriber’s profile is updated.
Ping Cluster
Pings the cluster to check its connectivity and health.
Subscribe Trigger
Fires when someone subscribes.
Unsubscribe Trigger
Fires when someone unsubscribes.
Connect any two apps with Notis in the middle.
Mailchimp and Elasticsearch, 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 Elasticsearch.