Integromat will automate processes that you currently handle manually. It is not only capable of connecting apps but can also transfer and transform data. It works 24 hours a day, seven days a week and does not require your intervention. Simply set Integromat to do what you want and let it work for you. Save your time!
Watches changes to issues and filter them via JQL. Requires JIRA Administrator rights to automatically register webhooks.
Watches Issues. You can use this module if you don't have Administrator rights in JIRA and ask your Administrator to register a webhook for you.
Watches for new customers.
Watches for new transactions.
Adds a new comment to an issue.
Adds an attachment to an issue.
Assigns the issue to the user. Use this module to assign issues for the users having “Assign Issue” permission, and not having the “Edit Issue” permission. If User Name parameter is set to “-1” then automatic issue assignee is used. An empty User Name will remove the assignee.
Creates a new issue.
Deletes a specific comment.
Deletes a specific issue.
Retrieves an attachment's metadata.
Retrieves an attachment and downloads it.
Retrieves an issue.
Performs an arbitrary authorized API call.
Removes a specific attachment.
Performs a transition on an issue.
Updates a comment.
Updates an issue.
Creates an issue when there is no id provided, otherwise updates the issue with the id provided.
Adds a given set of person records to a target static list. There is a limit of 300 lead ids per request. Required Permissions: Read-Write Lead
Associates a known Marketo lead record to a munchkin cookie and its associated web activity history. Required Permissions: Read-Write Lead
Remotely schedules a batch campaign to run at a given time. My tokens local to the campaign's parent program can be overridden for the run to customize content. When using the "cloneToProgramName" parameter described below, this endpoint is limited to 20 calls per day. Required Permissions: Execute Campaign
Passes a set of leads to a trigger campaign to run through the campaign's flow. The designated campaign must have a Campaign is Requested: Web Service API trigger, and must be active. My tokens local to the campaign's parent program can be overridden for the run to customize content. A maximum of 100 leads are allowed per call. Required Permissions: Execute Campaign
Creates a new customer.
Deletes a customer.
Performs an arbitrary authorized GraphQL query.
Retrieves a customer.
Retrieves a transaction.
Updates a customer.
Retrieves comments for a specific issue.
Searches issues using JQL.
Returns metadata about lead objects in the target instance, including a list of all fields available for interaction via the APIs.
Returns a set of static list records based on given filter parameters. Required Permissions: Read-Only Lead, Read-Write Lead
Checks if leads are members of a given static list. Required Permissions: Read-Write Lead
Returns a list of campaign records. Required Permissions: Read-Only Campaigns, Read-Write Campaigns
Returns a list of up to 300 leads based on a list of values in a particular field. Required Permissions: Read-Only Lead, Read-Write Lead
Retrieves a list of leads which are members of the designated program. Required Permissions: Read-Only Lead, Read-Write Lead
Retrieves person records which are members of the given static list. Required Permissions: Read-Only Lead, Read-Write Lead
Searches for customers.
Searches for transactions.