Conference & Event Location Tracker
Event decisions get scattered across comments without location context. This automation watches for conference mentions and instantly looks up location data--so your team sees where the event is, the local ecosystem, and market reach before deciding to attend.
Trigger
Comment Received Trigger
Triggered when a comment is received.
Action
Google Locations
Tool to retrieve google-supported locations. use when searching for locations by name. returns locations ordered by reach (most populous first).
Why this helps
Event opportunity discussions lack geographic context, leading to uninformed conference decisions
- Event location data automatically added to opportunity discussions
- Geographic context visible for each conference option
- Event decisions informed by location and local opportunity
- Event ROI assessment includes market reach data
Setup
Build it in a few focused steps.
- 1Set up Linear and Autom connections
- 2Ask Notis: 'When someone comments about a conference or event opportunity, look up location data for that city'
- 3Use 'Comment Received' as your trigger
- 4Select your notification channel
- 5Test by commenting 'should we sponsor TechCrunch Disrupt in Tokyo?' and verify location data appears
Questions about this workflow
Can I see how many potential customers are in each event location?
Location data includes population and local market info. Combine that with industry statistics for customer estimates.
What if the event moves to a new city?
Just mention the new city in a comment and Notis looks up data for the new location.
How do I calculate ROI for an event?
Use location market size and population to estimate potential leads. Compare event cost to addressable market.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Autom. A trigger fires from one place; an action lands in another.
Linear triggers
Autom actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Google Countries
Tool to list google-supported countries. use when you need to filter or suggest countries based on a search string.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Google Images
Tool to fetch images from google search results. use when you need urls, titles, domains, and metadata for images matching a query.
Comment Received Trigger
Triggered when a comment is received.
Google Languages
Tool to retrieve google-supported languages. use when you need a list of language codes for localization.
Issue Created Trigger
Triggered when a new issue is created.
Google Locations
Tool to retrieve google-supported locations. use when searching for locations by name. returns locations ordered by reach (most populous first).
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and Autom, 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 Autom.