Custom API Action

Make a custom HTTP Request to the Github API.


  • Request Type (dropdown): use the appropriate request type depending on the endpoint/method

    • GET

    • POST

    • PUT

    • PATCH

    • DELETE


  • Relative URL (text): The base URL is{{Relative-URL.Input-request}}.
Example of a relative URL for an input request: `/repos`.

Note: The version of the api is handled by the connector in the Accept header.

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

  • Headers (object): Specify any headers required in addition to authorization or content-type (these are already handled by this connector).

  • Body (object): Specify a request body in JSON format. Only available for POST, PUT, and PATCH requests.



  • Status Code (number): success or failure of your HTTP request. Here is a list of all status codes.

  • Headers (object): a 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 usually be a replica of the example below.

    Example: {"Content-type":"application/json"}
  • Body (object): data returned from your selected HTTP request (for example, the data from a GET request).

Related topics

GitHub connector

About the elements of Okta Workflows

GitHub API documentation