Skip to main content
日本語

Workflow Actions: How to Use HTTP Requests

Updated
[Notice of UI Terminology Changes]
With sequential updates, the term "Member" is being changed to "User" and "Employee ID" to "User ID" within the help pages. If "Member" or "Employee ID" is still displayed on your screen, please read them as "User" or "User ID" respectively when referring to this help documentation. For more details on the background of this change, please check this announcement.
Note: The screenshots in this article are currently taken from the Japanese version of the product. Some labels in the images may differ from the English interface.

Overview

By using the "HTTP Request" action, you can send data to external systems (IT tools such as Zendesk, Freshdesk, ServiceNow, etc.) or automatically create tickets while a workflow is running.

Setup Steps

  1. On the workflow editing screen, select HTTP Request from the action list.
  2. When the window opens on the right side, select the execution date and time for the HTTP request, and enter the cURL command you want to execute in the text box.
    Using Variables: You can send dynamic data by copying the variables displayed at the bottom of the text box (e.g., @Email, @location, etc.) and pasting them into your request.
  3. To verify that the configured request works correctly, click the "Test HTTP Request" button. Check if the expected response is returned.

Configuration Example: Creating a Ticket in an External Tool (cURL)

For example, to automatically create a ticket in Zendesk during an onboarding workflow, configure a request like the following:

Bash
curl --location 'https://[subdomain].zendesk.com/api/v2/tickets.json' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic [credentials]' \
--data-raw '{
 "ticket": {
   "subject": "IT Helpdesk - Onboarding Request",
   "comment": {
     "body": "Please add the following user to 1Password: @Email @location"
   },
   "assignee_id": "902343506386"
 }
}'

Available Variables

The following variables can be used in HTTP requests:

Variable Description
@User ID Retrieves the "User ID" of the triggered user from the User Profiles.
@Work Location Retrieves the "Work Location" of the triggered user from the User Profiles.
@First Name Retrieves the "First Name" of the triggered user from the User Profiles.
@Last Name Retrieves the "Last Name" of the triggered user from the User Profiles.
@App Name Retrieves the "Name" of the triggered app from the Apps.
@Workflow Type Retrieves the template name of the triggered workflow.
@Workflow Name Retrieves the name of the triggered workflow.
@Email Address Retrieves the "Email Address" of the triggered user from the User Profiles.
@Job Title Retrieves the "Job Title" of the triggered user from the User Profiles.
@User Type Retrieves the "User Type" of the triggered user from the User Profiles.
@App URL Retrieves the source URL of the triggered app if it was detected by the browser extension and has a source URL.

Related articles