Keep Apollo contact records current as Jira work changes
When a Jira update includes a meaningful change to a person's details, carry that update into their Apollo record.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
Update Apollo contact
Updates specified attributes of an existing apollo.io contact, identified by `contact id`; requires at least one other attribute to be provided for modification.
Why this helps
People's contact context changes during delivery work, and busy teams can leave Apollo records behind.
- Reflect relevant contact changes from Jira in Apollo.
- Limit updates to information present in the issue change.
- Reduce record maintenance after project conversations.
Setup
Build it in a few focused steps.
- 1Connect Jira and Apollo in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, tell Notis which supplied Jira changes should update an existing Apollo contact and how to identify that contact.
- 4Pick the Jira Updated Issue trigger and choose where run reports should go.
- 5Test with one real issue update that includes contact information.
Questions about this workflow
Can this update an existing contact without a contact identifier?
Notis needs enough information from Jira or your instruction to identify the Apollo contact. Ask it to report when it cannot confidently match a person.
Will it update every field in Apollo?
The action requires at least one attribute to change. Describe which available information should be updated; do not assume Jira supplies fields it does not contain.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Apollo. A trigger fires from one place; an action lands in another.
Jira triggers
Apollo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Contacts to Sequence
Adds contacts to a specified apollo email sequence by initiating an asynchronous background job and returning its details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Bulk organization enrichment
Enriches data for up to 10 organizations simultaneously by providing a list of their base company domains (e.g., 'apollo.io', not 'www.apollo.io').
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Bulk people enrichment
Use to enrich multiple person profiles simultaneously with comprehensive data from apollo's database.
New Project
Triggered when a new project is added in Jira
Bulk update account stage
Bulk updates the stage for specified existing apollo.io accounts, moving them to a valid new account stage.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Create an Apollo account
Creates a new account in apollo.io; a new record is created even if a similar account exists, and provided `owner id` or `account stage id` must be valid existing ids.
Create Apollo contact
Creates a new contact in apollo.io; use `account id` to link to an organization and `contact stage id` for sales stage, noting that apollo does not perform automatic deduplication.
Create Apollo deal
Creates a new sales opportunity (deal) in apollo.io; all provided ids (`owner id`, `account id`, `opportunity stage id`) must be valid existing apollo identifiers.
Create Apollo Task
Creates a distinct apollo.io task for each contact id in contact ids, assigning them to user id; this action is not for free plan users and repeated calls create duplicate tasks.
Connect any two apps with Notis in the middle.
Jira and Apollo, 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 Apollo.