Screen event leads by submitted location
After an event, submit the lead details and locations. Notis can check the locations against your Census criteria and create HubSpot contacts for the leads that fit.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create batch of contacts
Creates up to 100 new contact records in hubspot crm, optionally associating them with existing crm objects; ensure associated object ids are valid.
Why this helps
Post-event follow-up gets harder when the whole list enters the CRM before anyone checks market fit.
- Apply market criteria to event follow-up
- Keep submitted contact details together
- Reduce manual list screening
Setup
Build it in a few focused steps.
- 1Connect Census bureau and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, specify the location criteria, qualifying rules, and contact details to use from the submitted event list.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real event lead and confirm the created contact.
Questions about this workflow
Does Census supply event lead information?
No. Supply names, contact details, and locations from the event list. Census is used for aggregate statistics about those locations.
Can this create all the event leads at once?
The batch action supports up to 100 contacts per request. Split larger lists into suitable batches.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Census bureau to Hubspot. A trigger fires from one place; an action lands in another.
Census bureau triggers
Hubspot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add asset association
Associates an existing asset ('form', 'object list', or 'external web url') with a specified hubspot marketing campaign.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add token to event template
Adds a new custom data token to an existing event template for a specified hubspot application, optionally populating a crm object property if objectpropertyname is provided.
Archive email
Archives the hubspot email specified by `emailid` by moving it to the recycling bin, making it inaccessible unless restored.
Archive a batch of emails by ID
Archives multiple hubspot crm emails by id; ids must exist as archiving is irreversible.
Archive a batch of quotes by id
Archives a batch of existing, non-archived quotes by their ids; this action is irreversible and useful for managing outdated or irrelevant quotes.
Archive batch of companies by id
Archives a batch of companies by their unique ids; targeted companies must exist, not be previously archived, and this api operation is irreversible.
Archive batch of contacts by id
Archives a batch of existing contacts by their hubspot crm ids, rendering them inactive; this action is irreversible via the api and requires manual restoration or a separate unarchive endpoint.
Archive batch of deals by id
Archives a batch of existing deals by their unique hubspot ids, removing them from active views and reports (soft delete); archived deals may be restorable.
Connect any two apps with Notis in the middle.
Census bureau and Hubspot, 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 Hubspot.