AppsPricingBlogTry it
Teamwork logo
Jira logo

Connect Teamwork to Jira

Use 5 documented Teamwork triggers to run 24 documented Jira actions.

5 source triggers
24 target actions
Reverse direction supported

Why Connect Teamwork & Jira?

Start with a Teamwork event

Choose from 5 documented triggers, including New Task (Instant), New Task Deleted (Instant), New Task Updated (Instant).

Run a Jira action

Send the event into one of 24 documented actions, such as Add Attachment To Issue, Add Comment To Issue, Add Multiple Attachments To Issue.

Map and review the workflow

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

Available Triggers & Actions

Teamwork logo

Teamwork

Triggers (5)

New Task (Instant)

Emit new event when a new task is created

webhook
New Task Deleted (Instant)

Emit new event when a new task is deleted

webhook
New Task Updated (Instant)

Emit new event when a new task is updated

webhook
New User Created (Instant)

Emit new event when a new user is created

webhook
User Updated (Instant)

Emit new event when a user is updated

webhook

Actions (10)

Create Task

Create a new task in the backlog. See the docs here

Create User

Create a new user in Teamwork. See the docs here

Delete Task

Delete a task. See the docs here

Get User

Get a user by ID. See the documentation

List Company ID Options

Retrieves available options for the Company ID field.

List People Id Options

Retrieves available options for the People Id field.

List Project Tasks

List tasks from a project. See the docs here

List Users

List all users. See the documentation

Update Task

Update a task. See the docs here

Update User

Update a user in Teamwork. See the documentation

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

Integration Features

5 documented Teamwork triggers
24 documented Jira actions
Configurable field mapping
Conditional workflow steps
Execution monitoring
A supported Jira to Teamwork direction

Capability Examples

Teamwork trigger → Jira action

Catalog example
TeamworkTeamwork

New Task (Instant)

JiraJira

Add Attachment To Issue

Jira trigger → Teamwork action

Reverse direction
JiraJira

New Event

TeamworkTeamwork

Create Task

How It Works

1

Connect Apps

Authenticate your Teamwork and Jira accounts

2

Choose a Trigger

Select a documented Teamwork event

3

Choose an Action

Select the documented Jira 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 5 documented Teamwork triggers.

Automated Actions

Run one of 24 documented Jira 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 logoTeamwork logo

Reverse Integration Available

Also connect Jira to Teamwork for bidirectional automation

View Integration
Teamwork logo

All Teamwork Integrations

Explore all available Teamwork connections

View All Integrations
Jira logo

All Jira Integrations

Explore all available Jira connections

View All Integrations

Ready to Connect Teamwork & Jira?

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

Get Started Free