T.I.L Pill | Custom PUT and POST Requests in Alteryx

You may be familiar with the standard HTTP actions in the Alteryx Download tool. In this edition of T.I.L Pill, we will quickly explore how to leverage the “Custom” option to perform custom "PUT" and "GET" HTTP actions in Alteryx's Download tool. It is super easy (and quick) and to do, but it allows you so much more freedom with your API calls!

By default, the Alteryx Download tool provides several standard actions such as GET, PUT, and POST, which handles most typical use cases. However, there are instances where you need to use alternative methods, such as:

  • Making a GET call without the "Take Query String/Body from Field" adding the information as query string instead of body (and not use a "Blob" type field)
  • Use a PUT request with a dynamic body from an existing field (and not use a Blob type field)
  • Or just not using a Blob type field (sorry Blobs)

Using the standard HTTP actions can restrict your choice of options, requiring static text or Blob fields. These are not always desired because sometimes you need you body to dynamically change to your workflow’s state or adding a Blob convert tool adds unnecessary complexity and may not work the way you would like. Or maybe you are still not used to how Alteryx’s download tool does things and you colleague across from wrote out a working Python in 10 seconds flat. This is where the Custom option comes into play.

You may already be familiar with using the Custom option for other commands, like DELETE, HEAD, or PATCH. However, from the multiple posts in the Alteryx forums, there’s a sense that many don’t know that you can customize the standard ones!

Leveraging the Custom Option for HTTP Actions
To perform a custom PUT, GET, (or honestly any HTTP) action using Alteryx's Download tool, follow these really simple steps:

  1. Go to your download tool configuration pane
  2. In the Payload tab, set the HTTP Action to Custom
  3. In the text field next to Custom, enter the HTTP Action you want to perform (ex. PUT)
  4. Select the radial button “Take Query String/Body from Field" and select the field you have the request body in
Screenshot 2019-05-08 at 16.20.22.png

And that’s it! You now have your very own customized version of the standard HTTP actions.

Author:
Marc-Anthony Tucker
Powered by The Information Lab
1st Floor, 25 Watling Street, London, EC4M 9BR
Subscribe
to our Newsletter
Get the lastest news about The Data School and application tips
Subscribe now
© 2025 The Information Lab