Keep scripture follow-up contacts current
Use a recurring run to process the follow-up list you provide and add its people to HubSpot.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
People asking for scripture resources can slip through when a separate follow-up list is not revisited.
- Process a user-provided follow-up list on a recurring schedule
- Keep resource requests available in HubSpot
- Avoid relying on memory to revisit the list
Setup
Build it in a few focused steps.
- 1Connect Api bible and HubSpot once in the Notis portal.
- 2Create an automation and name it for scripture follow-up.
- 3Tell Notis in one instruction to create HubSpot contacts from the follow-up records you provide for people requesting scripture resources.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real record from your supplied list and review the result.
Questions about this workflow
Does this find people who asked a scripture question in Api bible?
No. Api bible exposes no trigger events, and this workflow needs you to provide the follow-up records.
Can the schedule supply records by itself?
The schedule starts the run, but the people and their details must come from data you provide to Notis.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Api bible to Hubspot. A trigger fires from one place; an action lands in another.
Api bible 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.
Api bible 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.