AppsPricingBlogTry it
Smoove logo
Jira logo

Connect Smoove to Jira

Use 3 documented Smoove triggers to run 24 documented Jira actions.

3 source triggers
24 target actions
Reverse direction supported

Why Connect Smoove & Jira?

Start with a Smoove event

Choose from 3 documented triggers, including New Form Created, New List Created, New Subscriber Created.

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

Smoove logo

Smoove

Triggers (3)

New Form Created

Emit new event when a new form is created. See the docs.

polling
New List Created

Emit new event when a new list is created. See the docs.

polling
New Subscriber Created

Emit new event when a new subscriber is created. See the docs.

polling

Actions (5)

Add Or Update Subscriber

Adds a new contact to your account or update an existing contact. See the docs.

Create List

Creates a new list. See the docs.

Find Or Create Subscriber

Checks if a contact exists in your account otherwise will create a contact. See the docs.

Find Subscriber

Contacts information can be retrieved by sending the function a unique identifier (contact's ID, email, cell phone or external ID). See the docs.

Unsubscribe

Unsubscribes a contact. See the docs.

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

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

Capability Examples

Smoove trigger → Jira action

Catalog example
SmooveSmoove

New Form Created

JiraJira

Add Attachment To Issue

Jira trigger → Smoove action

Reverse direction
JiraJira

New Event

SmooveSmoove

Add Or Update Subscriber

How It Works

1

Connect Apps

Authenticate your Smoove and Jira accounts

2

Choose a Trigger

Select a documented Smoove 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 3 documented Smoove 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 logoSmoove logo

Reverse Integration Available

Also connect Jira to Smoove for bidirectional automation

View Integration
Smoove logo

All Smoove Integrations

Explore all available Smoove connections

View All Integrations
Jira logo

All Jira Integrations

Explore all available Jira connections

View All Integrations

Ready to Connect Smoove & Jira?

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

Get Started Free