Skip to main content

Perform an API call

Performs an API call in IntakeQ. Please refer to the API documentation for more details on configuration.

API doc: https://support.intakeq.com/article/31-intakeq-api

Application​

  • IntakeQ

Inputs (what you have)​

For URL-encoded form data, see Sending URL-encoded form data.

NameDescriptionData TypeRequired?Example
Connected AccountThe Connected Account to use for the requestConnected AccountYes
EndpointThe URL of the API endpoint to accessText (Long)Yeshttps://intakeq.com/api/v1/clients
MethodThe HTTP method to be used for the requestPredefined Choice ListYesGET
Request headersAdditional headers to include in the request in JSON format. The X-Auth-Key header is added automatically from the connected account.Text (Long)No{"Content-Type": "application/json"}
Request bodyThe data to be included in the request bodyText (Long)No{"name": "John", "age": 25}
FileA file to be included in the request. Note: If a file is added, leave request headers blank and add a filename in your request body.FileNoexample.png
Output response as a file?Select this as true when your API call returns a file as an outputTrue/FalseNo

Note: the value of inputs can either be a set value in the configuration of the Wrk Action within the Wrkflow, or a variable from the Data Library section. These variables in the Data Library section are the outputs of previous Wrk Actions in the Wrkflow.

Outputs (what you get)​

NameData TypeDescriptionRequired?Example
Response status codeIntegerThe HTTP status code returned in the responseYes200
Response headersText (Long)Additional information provided in the response headersNoContent-Type: application/json
Response bodyText (Long)The main content of the responseNo{"message": "Success"}
Downloaded fileFileA file that is downloaded as part of the responseNoexample.pdf

Note: Use Custom Outputs to create named outputs from this Wrk Action's JSON outputs. Choose the source output and, for Text (short) or Text (long) fields, provide a JSONPath such as $.message; top-level paths remain supported alongside nested and advanced JSONPath expressions.

Outcomes​

NameDescription
SuccessThis status is selected in the event that the API call returns with a status between 200-399
UnsuccessfulThis status is selected in the event that the API call returns with a status of 400+
Impossible to CompleteThis status is selected in the event of the following scenario:Couldn't resolve hostnameThe external system is not accessible

Requirements​

  • An IntakeQ connected account with API access enabled. Find your API key under More → Settings → Integrations → Developer API.