Skip to main content

Requests overview

Discover different request types to extend the functionality of your actions

Requests in Actioner are used to specify how your action communicates with your tools. You can

  • generate values for your input and output components
  • specify what to perform in your tools
  • perform Slack-native functions such as creating a collaboration channel, mentioning users for approval or posting a message in your channel
  • add utility functions such as calculations, translations, weather status or gifs from Giphy.
  • open external links
  • create, update or delete scheduled jobs
  • perform operations on the records of your tables in your apps

Request types​

There are 4 types of requests in Actioner: API, link, Slack and utilities.

  1. API requests are used for retrieving dynamic values for input and output components. You can get the list of projects for Show deals action and prompt users to select a deal while running the action. You can get the list of users and while listing deals on a table output, you can display the names of deal owners instead of their ids.
    An API request is also used to perform an operation in your application. For Get support from IT action, you can configure an API request that creates a new Zendesk ticket.

  2. Slack requests are used for executing Slack native functions, such as sending an approval request to your manager or creating a collaboration channel.

  3. Utility requests are used for specific functions natively provided by Actioner. Getting the weather status or a translation of a phrase or inserting gifs from Giphy to your outputs or Slack markdown blocks are some utility functions you can enrich your actions with.

  4. Link requests are used for opening external links in a new tab.

  5. Job requests are used to create, update or delete scheduled jobs.

  6. Table requests are used to perform operations on the records of your tables in your apps.

Requests tab​

To see and update the request components of your action, open your action in Design mode and navigate to Requests tab.

Use Show requests and Hide requests buttons to show or hide Requests tab.

Adding a new request​

Click + Add request to add a new request to your action. Select request type and give a name to your request. If you are adding a Slack or a utility request, also select the type of the event from the dropdown.

Add a new request

Updating a request​

Click on a request to view or update its configurations. You can configure the request on the right panel.

Updating request name and type​

To update the name of your request, you can click on the pen icon.

Update the name of a request

Cloning requests​

Click ellipsis … at top right corner of your request and select Clone to clone a request.

Clone a request

When you clone a request

  • Destination action becomes DRAFT - whether the destination action is the same with or diffent from the cloned action.
  • If the destination action was already DRAFT, the request is cloned to the DRAFT version.

Cloning an API request​

When you clone an API request within the same action, a new API request is created with the same connection.

When you clone an API request to another action, Actioner shows you the dependencies. You may select to clone the connection or not.

Note

Credentials of a connection is never copied.

If you are cloning the API request to another action and if the destination action contains a connection with the same name, clone the connection without selecting connection dependencies. In that case, do not forget to select a connection for the cloned API request.

Cloning a Slack request​

When you clone a Slack request within the same action, a new Slack request is created with the same Slack connection. When you clone a Slack request to another action, Actioner shows you the dependencies. You may select to clone the Slack connection or not.

If you are cloning the Slack request to another action and if the destination action contains a connection with the same name,clone the connection without selecting the Slack connection in the dependencies. In that case, do not forget to select a connection for the cloned Slack request.

Cloning a utility request​

When a utility request is cloned, a new utility request is created in the destination action with the name you give while cloning.

When a link request is cloned, a new link request is created in the destination action with the same URL and the name you give while cloning.

Cloning a job request​

When a job request is cloned, a new job request is created in the destination action with the same parameters and the name you give while cloning.

Cloning a table request​

When a table request is cloned, a new table request is created in the destination action with the same fields and the name you give while cloning.

Deleting requests​

Click ellipsis … and select Delete to remove a request from your action.

Delete a request