AppsPricingBlogTry it
Jira logo
Apollo logo

Connect Jira to Apollo

Use 4 documented Jira triggers to run 10 documented Apollo actions.

4 source triggers
10 target actions

Why Connect Jira & Apollo?

Start with a Jira event

Choose from 4 documented triggers, including New Event, New Issue Created Event (Instant), New Issue Deleted Event (Instant).

Run a Apollo action

Send the event into one of 10 documented actions, such as Add Contacts to Sequence, Create or Update Account, Create or Update Contact.

Map and review the workflow

Choose the fields and conditions for the workflow, then test the result before activation.

Available Triggers & Actions

Jira logo

Jira

Triggers (4)

New Event

Emit new event when an event with subscribed event source triggered, See the documentation

webhook
New Issue Created Event (Instant)

Emit new event when an issue is created. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook
New Issue Deleted Event (Instant)

Emit new event when an issue is deleted. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook
New Issue Updated Event (Instant)

Emit new event when an issue is updated. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook

Actions (24)

Add Attachment To Issue

Adds an attachment to an issue. See the documentation

Add Comment To Issue

Adds a new comment to an issue. See the documentation

Add Multiple Attachments To Issue

Adds multiple attachments to an issue. See the documentation

Add Watcher To Issue

Adds a user as a watcher of an issue by passing the account ID of the user, For example, 5b10ac8d82e05b22cc7d4ef5, If no user is specified the calling user is added. See the documentation

Assign Issue

Assigns an issue to a user. See the documentation

Check Issues Against JQL

Checks whether one or more issues would be returned by one or more JQL queries. See the documentation

Count Issues Using JQL

Provide an estimated count of the issues that match the JQL. See the documentation

Create Custom Field Options (Context)

Create a context for custom field options. See the documentation.

Create Future Sprint

Creates a future sprint. See the documentation

Create Issue

Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask. See the documentation

Create Jira Version in Project

Creates a project version. See the documentation

Delete Project

Deletes a project. See the documentation

Get All Projects

Gets metadata on all projects. See the documentation

Get Board

Returns the board for the given board ID. See the documentation

Get Cloud ID

Gets the cloud ID and details of all accessible Jira Cloud sites. See the documentation

Get Current User

Returns the authenticated Jira user's account ID, display name, email, and active status. Call this first when the user says 'my issues', 'assigned to me', or needs their Jira identity. Use the returned accountId with **Search Issues with JQL** (e.g. assignee = '{accountId}') or **Assign Issue**. Requires a Cloud ID to identify the Jira site. See the documentation.

Get Issue

Gets the details for an issue. See the documentation

Get Issue Picker Suggestions

Returns lists of issues matching a query string. See the documentation

Get Issue Types

Gets the available issue types. If a project ID is provided, returns issue types for that project. Otherwise, returns all issue types accessible to the user. See the documentation

Get Sprint

Returns the sprint for a given sprint ID. See the documentation

Get Task

Gets the status of a long-running asynchronous task. See the documentation

Get Transitions

Gets either all transitions or a transition that can be performed by the user on an issue, based on the issue's status. See the documentation

Get User

Gets details of user. See the documentation

Get Users

Gets the details for a list of users. See the documentation

Apollo logo

Apollo

Actions (10)

Add Contacts to Sequence

Adds one or more contacts to an email outreach sequence in Apollo. Requires a sequence ID, contact IDs, and a sending email account ID. Use **List Metadata** (type sequences) to find sequence IDs, (type email_accounts) to find email account IDs. Use **Search Contacts** to find contact IDs to enroll. Set sequenceActiveInOtherCampaigns to true to enroll contacts already active in other sequences. See the documentation

Create or Update Account

Creates a new account (company) or updates an existing one in your Apollo CRM. To create, omit accountId and provide at least a name. To update, provide the accountId and any fields to change. Use **Search Accounts** to find existing accounts before updating. Use **List Metadata** (type account_stages) to discover valid stage IDs. See the documentation

Create or Update Contact

Creates a new contact or updates an existing one in your Apollo CRM. To create, omit contactId and provide at least an email. To update, provide the contactId and any fields to change. Use **Search Contacts** to find existing contacts by name or email before updating. Use **List Metadata** (type contact_stages) to discover valid stage IDs. The accountId links this contact to a company — use **Search Accounts** to find the account ID. See the documentation

Create or Update Opportunity

Creates a new opportunity (deal) or updates an existing one in your Apollo CRM. To create, omit opportunityId and provide name, opportunityStageId, closedDate, and accountId. To update, provide the opportunityId and any fields to change. Use **Get Opportunity** to fetch current details before updating. Use **List Metadata** (type opportunity_stages) to discover valid stage IDs, and **Search Accounts** to find account IDs. Use **Get Current User** to find owner IDs. See the documentation

Enrich Person

Enriches a person's information using Apollo's 270M+ contact database. Pass any combination of name, email, domain, organization, or LinkedIn URL — the more info you provide, the better the match. This action consumes Apollo enrichment credits. Returns detailed profile data including title, company, seniority, phone numbers, and social profiles. Do NOT pass personal social media URLs as the domain — use only company domains like apollo.io. If revealPhoneNumber is true, you must also provide a webhookUrl where Apollo will POST the phone data asynchronously. See the documentation

Get Current User

Returns the authenticated user's profile including their ID, name, email, and team information. Use this tool first to identify the current user's ID for filtering records by owner in **Search Contacts** or **Search Accounts**. See the documentation

Get Opportunity

Fetches a single opportunity (deal) by ID with full details including name, amount, stage, close date, owner, and linked account. Use **Create or Update Opportunity** to modify it after retrieval. See the documentation

List Metadata

Lists metadata such as stages, sequences, labels, email accounts, or team users. Use this tool to discover valid IDs before calling write tools — e.g., find a contact stage ID for **Create or Update Contact**, a sequence ID for **Add Contacts to Sequence**, or an opportunity stage ID for **Create or Update Opportunity**. See the documentation

Search Accounts

Searches for accounts (companies) in your Apollo CRM by name, stage, or sort criteria. Returns account name, domain, industry, and stage. Use this to find accounts before updating them with **Create or Update Account** or linking them to contacts or opportunities. See the documentation

Search Contacts

Searches for contacts in your Apollo CRM by keyword, stage, or sort criteria. Returns contact name, email, title, company, and stage. Use this to find contacts before updating them with **Create or Update Contact** or enrolling them with **Add Contacts to Sequence**. The query parameter searches across name, title, company, and email. See the documentation

Integration Features

4 documented Jira triggers
10 documented Apollo actions
Configurable field mapping
Conditional workflow steps
Execution monitoring

Capability Examples

Jira trigger → Apollo action

Catalog example
JiraJira

New Event

ApolloApollo

Add Contacts to Sequence

How It Works

1

Connect Apps

Authenticate your Jira and Apollo accounts

2

Choose a Trigger

Select a documented Jira event

3

Choose an Action

Select the documented Apollo operation to run

Test and Review

Verify field mapping and provider responses before activation

Frequently Asked Questions

Integration Benefits

Trigger-driven Workflows

Start the supported direction from one of 4 documented Jira triggers.

Automated Actions

Run one of 10 documented Apollo actions after the selected trigger fires.

Provider Authentication

Review the authentication requirements published by each provider before activating the workflow.

Guided Configuration

Select a documented trigger, choose a target action, and map the fields required by the workflow.

Field Mapping

Map the fields exposed by the selected trigger and action, then review the required provider inputs.

Execution Review

Test the workflow and review provider responses before relying on it in production.

Jira logo

All Jira Integrations

Explore all available Jira connections

View All Integrations
Apollo logo

All Apollo Integrations

Explore all available Apollo connections

View All Integrations

Ready to Connect Jira & Apollo?

Build this supported workflow in Mazaal AI and test it with your own provider accounts.

Get Started Free