Custom API Action

Make a custom, authenticated HTTP call to the Jira Service Desk API.

This action is unlike other Jira Service Desk cards. See Jira Service Desk API documentation for more information on using custom HTTP calls.

Options

Field Definition Type Required
Request Type These are supported HTTP request methods, or HTTP verbs, in a custom API call (see HTTP request methods).
  • GET: Retrieves data from a web server based on parameters. This method requests a representation of the specified resource. If a request is successful, a 200 (OK) response message is returned with the requested content.
  • POST: Sends data to a web server based on parameters (for example, uploading a file). Multiple POST requests may result in a different outcome than a single POST. Caution should be exercised to avoid sending multiple POST requests unintentionally. If a request is successful, a 200 (OK) response message is returned.
  • PUT: Sends data to be stored at a specific location on a web server based on parameters (for example, uploading a file). Unlike POST requests, PUT requests are idempotent. For successful requests, the result of a single PUT request is the same as many identical PUT requests. If a request is successful, a 200 (OK), 201 (Created), or 204 (No Content) response message is returned.
  • PATCH: Applies partial modifications to a resource on a web server based on parameters. PATCH is not idempotent. Multiple PATCH requests could have unintended consequences. If a PATCH is successful, a 200 (OK) or 204 (No Content) response message is returned.
  • DELETE: Deletes the specified resource (if it exists) from the web server based on parameters. If a DELETE is successful, a 200 (OK) response message is returned.
Dropdown TRUE

Input

Field Definition Type Required
Request
Relative URL URL address on the web server to which you are attempting to interact. Specify the relative URL as /{insert_remaining_URL}. You can specify query parameters in the relative URL using "?", or specify the query parameters as an object key pair in the Query input.

For example:

https://{Subdomain}.atlassian.net/rest/api/2/issue/{Issue ID}/transitions the relative URL is /rest/api/2/issue/{Issue ID}/transitions.

Webhook examples:

https://{Subdomain}.atlassian.net/rest/api/2/issue/{Issue ID}/transitions the relative URL is /rest/api/2/issue/{Issue ID}/transitions.

https://{Subdomain}.atlassian.net/rest/webhooks/1.0/webhook the relative URL is /webhooks/1.0/webhook.

See G Suite API documentation

String FALSE
Query Specify any additional query parameters that should be included in object format (key value pairs).

Example: {"name":"something-urgent"}

Object or string FALSE
Headers Specify any headers required in addition to authorization or content-type (these are already handled by this connector). This will usually be similar to the following:

Example: {"Content-type":"application/json"}

Object FALSE
Body Specify a request body in JSON format. Only available for POST, PUT, and PATCH requests. Object FALSE

Output

Field Definition Type
Response    
Status Code Result of the operation. The HTTP status code is returned by the connector and indicates whether the action taken by the card succeeded or failed. For example:
  • A 201 Created status code indicates success where a new resource was created.
  • A 403 Forbidden error indicates that the HTTP request was not processed because the necessary permissions were missing.

For a full list of possible status codes, see HTTP status codes.

Number
Headers Detailed context for the status code, unrelated to the output body. Response headers are dependent on your selected HTTP request option. Note that not all headers are response headers. This will be usually similar to {"Content-type":"application/json"}. Object
Body

Data returned from your selected HTTP request.

For example, the data from a GET request.

Object

Related topics

Google Drive connector

Elements of Workflows

G Suite API documentation