Prerequisites

1. The third-party software has a public REST API.
2. The third-party API uses a static authorization header (not OAuth or a dynamic token).
3. The third-party API provides the action you want via a standard HTTP request.
4. You can accomplish the action in a single HTTP request. Torii does not currently support storing data from a GET request for use in a subsequent action. 

Introduction

Custom actions are an advanced workflow feature that allows you to interact with any 3rd party software that has an API. Here are some examples that can be done:

• Integrating with Zapier / Workato / integromat by sending a webhook

• Sending a message to Microsoft Teams or Google Chat
• Creating a Jira or ServiceNow ticket

• Sending a highly customized message to Slack

• Interacting with software built in-house

• Sending a webhook from Torii

How to Use?

Start by creating a workflow in Torii from the Workflows page and add a trigger that will control when the workflow should run.

Step 1 — Add a custom action to a workflow

Now, add the "Custom action (HTTP Request)" by picking it from the list:

Step 2 — Add description (optional)

We recommend adding a short description that briefly describes what the custom action is supposed to do.

Step 3 — Choose HTTP method

Pick the method of the HTTP request:

Step 4 — Choose URL

Choose the URL to send the request to. In this example, we are using a Zapier webhook:

Step 5 — Add Query Parameters (optional)

You can now add Query Parameters to the request by providing key and value pairs.

You can use @ to customize the value field.

Step 6 — Add headers (optional)

If your request requires additional headers, for authentication, for example, you can add them as key-value pairs:

If you need to add an authorization header, please note that Torii only supports static tokens, not dynamic tokens or OAuth.

You can use @ to customize the value field.

Step 7 — Add body (optional)

You can add a body with a valid JSON payload. In this example, we are sending a JSON payload and using the @ to add customization:

Important remark - If you need to define some inner json object as part of the body definition, you should make sure the opening\closing braces ( '{' and '}' ) are not on the same line.
e.g. define it like this

Testing the Custom Action

You can test the custom action by clicking the Run now button of the workflow.