HTTP

http is the fundamental component of data transfer for the world wide web with the http app in {{product name}} , you can download web pages, access files, make api calls, and trigger webhooks you do not need to establish a connection to use most of the http app modules http modules select a module of the http app based on the authentication requirements of the resource you want to use to use modules that require authentication, you have to create a connection first actions get a file downloads a file from a url field description url enter the url of the file you want to download you can use the file (map the file data) in other modules in the {{scenario singular lowercase}} make a basic auth request sends an http request with basic authentication the output bundle contains the http response field description credentials click add to add your credentials (user name and password) for basic authentication evaluate all states as errors (except for 2xx and 3xx) use the response status to detect errors otherwise, the module reports only {{product name}} related errors (like mapping errors or missing required values) url enter the request url serialize url encodes the api call url with the url encoding (encoding special characters for example) method select the http method you want to use get to retrieve information for an entry post to create a new entry put to update/replace an existing entry patch to make a partial entry update delete to delete an entry headers enter request headers for example, the response content type the http app requests do not have the accept header if the http request returns an unexpected response, try adding the accept / header query string enter the query key value pairs body type http body contains the data transferred in an http request the raw body type is suitable for most http requests, even if the app documentation does not specify the data type specify the data format of the body content in the content type field the application/x www form urlencoded body type is to post data using application/x www form urlencoded for application/x www form urlencoded , the body of the http request sent to the server is one query string the keys and values are encoded in key value pairs separated by & and with a = between the key and the value for binary data, use the multipart/form data body type instead example of the resulting http request format field1=value1\&field2=value2 use the multipart/form data content type to send files in the http request add fields to the request each field must contain a key value pair text enter the key and value to send in the request body file enter the key, and specify the source file you want to send in the request body map the file you want to upload from the previous module (for example http > get a file or google drive > download a file ), or enter the file name and file data manually parse response enable to parse http responses into bundles with this option, you don't need to add the parse json or parse xml modules otherwise, the http module returns the raw response data before you can use parsed json or xml content, run the module once manually so that the module can recognize the response content and allow you to map it in subsequent modules timeout specify the request timeout in seconds (1 300) default 40 seconds share cookies with other http modules enable to share cookies from the server with all http modules in your make self signed certificate upload your certificate if you want to use tls using your self signed certificate reject connections that use unverified (self signed) certificates enable to reject connections that use unverified tls certificates follow redirect enable to follow url redirects that return 3xx response statuses follow all redirect enable to follow url redirects regardless of response statuses disable serialization of multiple same query string keys as arrays make handles multiple values for the same url query string parameter key as arrays (e g , www test com?foo=bar\&foo=baz will be converted to www test com?foo\[0]=bar\&foo\[1]=baz ) enable to deactivate this behavior request compressed content enable to request compression of the response data adds the accept encoding header use mutual tls select if you want to use mutual tls (mtls) for the http request to ensure both the client and server authenticate each other using certificates make a client certificate auth request sends an http(s) request to apps that require a client certificate authorization field description evaluate all states as errors (except for 2xx and 3xx) use the response status to detect errors otherwise, the module reports only {{product name}} related errors (like mapping errors or missing required values) url enter the request url serialize url encodes the api call url with the url encoding (encoding special characters for example) method select the http method you want to use get to retrieve information for an entry post to create a new entry put to update/replace an existing entry patch to make a partial entry update delete to delete an entry headers enter request headers for example, the response content type the http app requests do not have the accept header if the http request returns an unexpected response, try adding the accept / header query string enter the query key value pairs body type http body contains the data transferred in an http request the raw body type is suitable for most http requests, even if the app documentation does not specify the data type specify the data format of the body content in the content type field the application/x www form urlencoded body type is to post data using application/x www form urlencoded for application/x www form urlencoded , the body of the http request sent to the server is one query string the keys and values are encoded in key value pairs separated by & and with a = between the key and the value for binary data, use the multipart/form data body type instead example of the resulting http request format field1=value1\&field2=value2 use the multipart/form data content type to send files in the http request add fields to the request each field must contain a key value pair text enter the key and value to send in the request body file enter the key, and specify the source file you want to send in the request body map the file you want to upload from the previous module (for example http > get a file or google drive > download a file ), or enter the file name and file data manually parse response enable to parse http responses into bundles with this option, you don't need to add the parse json or parse xml modules otherwise, the http module returns the raw response data before you can use parsed json or xml content, run the module once manually so that the module can recognize the response content and allow you to map it in subsequent modules timeout specify the request timeout in seconds (1 300) default 40 seconds share cookies with other http modules enable to share cookies from the server with all http modules in your make self signed certificate upload your certificate if you want to use tls using your self signed certificate reject connections that use unverified (self signed) certificates enable to reject connections that use unverified tls certificates follow redirect enable to follow url redirects that return 3xx response statuses follow all redirect enable to follow url redirects regardless of response statuses disable serialization of multiple same query string keys as arrays make handles multiple values for the same url query string parameter key as arrays (e g , www test com?foo=bar\&foo=baz will be converted to www test com?foo\[0]=bar\&foo\[1]=baz ) enable to deactivate this behavior request compressed content enable to request compression of the response data adds the accept encoding header use mutual tls select if you want to use mutual tls (mtls) for the http request to ensure both the client and server authenticate each other using certificates make an api key auth request sends an https request to a specified url that requires api key authorization and processes the response the output bundle contains the http response in the make an api key auth request module settings, click the add button the add a new keychain window pops up enter the following field value name the label for your api key connection key the api key to authorize the http calls if the api uses "bearer" or "token" authorization, add the word before the api key example bearer 1234 5678 abcd efgh api key placement select if you want the authorization in the request header or query string api key parameter name the name of the parameter that contains the api key click create to create the connection you created an api connection you can now use the connection in the module module settings field description evaluate all states as errors (except for 2xx and 3xx) use the response status to detect errors otherwise, the module reports only {{product name}} related errors (like mapping errors or missing required values) url enter the request url serialize url encodes the api call url with the url encoding (encoding special characters for example) method select the http method you want to use get to retrieve information for an entry post to create a new entry put to update/replace an existing entry patch to make a partial entry update delete to delete an entry headers enter request headers for example, the response content type the http app requests do not have the accept header if the http request returns an unexpected response, try adding the accept / header query string enter the query key value pairs body type http body contains the data transferred in an http request the raw body type is suitable for most http requests, even if the app documentation does not specify the data type specify the data format of the body content in the content type field the application/x www form urlencoded body type is to post data using application/x www form urlencoded for application/x www form urlencoded , the body of the http request sent to the server is one query string the keys and values are encoded in key value pairs separated by & and with a = between the key and the value for binary data, use the multipart/form data body type instead example of the resulting http request format field1=value1\&field2=value2 use the multipart/form data content type to send files in the http request add fields to the request each field must contain a key value pair text enter the key and value to send in the request body file enter the key, and specify the source file you want to send in the request body map the file you want to upload from the previous module (for example http > get a file or google drive > download a file ), or enter the file name and file data manually parse response enable to parse http responses into bundles with this option, you don't need to add the parse json or parse xml modules otherwise, the http module returns the raw response data before you can use parsed json or xml content, run the module once manually so that the module can recognize the response content and allow you to map it in subsequent modules timeout specify the request timeout in seconds (1 300) default 40 seconds share cookies with other http modules enable to share cookies from the server with all http modules in your make self signed certificate upload your certificate if you want to use tls using your self signed certificate reject connections that use unverified (self signed) certificates enable to reject connections that use unverified tls certificates follow redirect enable to follow url redirects that return 3xx response statuses follow all redirect enable to follow url redirects regardless of response statuses disable serialization of multiple same query string keys as arrays make handles multiple values for the same url query string parameter key as arrays (e g , www test com?foo=bar\&foo=baz will be converted to www test com?foo\[0]=bar\&foo\[1]=baz ) enable to deactivate this behavior request compressed content enable to request compression of the response data adds the accept encoding header use mutual tls select if you want to use mutual tls (mtls) for the http request to ensure both the client and server authenticate each other using certificates make an oauth 2 0 request sends an http(s) request to a specified url that requires oauth 2 0 authorization and processes the response in order to make http(s) requests that require an oauth 2 0 authorization, you need to create an oauth connection first create an oauth 2 0 connection {{product name}} supports two flows authorization code enter an authorize url and token url from the app api documentation implicit enter the authorize url from the app api documentation prerequisites an app account access to a developer portal or settings a redirect url (sometimes called a callback url) obtaining credentials in the app create an oauth client in the app that you want to connect with {{product name}} to do this, enter the developer portal or settings specify a redirect url https //www integromat com/oauth/cb/oauth2 obtain the client id and client secret sometimes the app calls them app key and app secret save the client id and client secret in a safe place you will need them when building a scenario in make find the authorize url and token url in the app api documentation these are the addresses through which make communicates with the app establishing the connection in make once you have your credentials from the app, you can enter them in the app's configuration in {{product name}} go to a {{scenario singular lowercase}} add the http make an oauth 2 0 request module click create a connection optional in the connection name field, enter a name for the connection in the flow type field, select the flow in the scopes field, add api scopes refer to the app api documentation to get scopes in the client id and client secret fields, enter the credentials you saved previously click save to create an oauth 2 0 connection you have created an oauth 2 0 connection now you can use the connection in the make an oauth 2 0 request module check the advanced settings to create a connection field description scope separator select the separator for the list of scopes you entered above check the app api documentation for the format of the list of scopes if the separator is not set correctly, make will be unable to create the connection, and you will receive an invalid scope error authorize parameters enter additional authorization request parameters as a key value pair response type code for the authorization code flow and token for the implicit flow redirect uri https //www integromat com/oauth/cb/oauth2 client id the client id you entered when creating an account access token parameters enter additional access token request parameters as key value pairs standard parameters grant type authorization code redirect uri https //www integromat com/oauth/cb/oauth2 client id the client id you entered when creating an account client secret the client secret you entered when creating the account code the code returned by the authorization request refresh token parameters enter the additional refresh token request paramters as key value pairs standard parameters grant type refresh token refresh token the refresh token obtained together with the access token client id the client id you entered when creating the account client secret the client secret you entered when creating the account custom headers specify any custom headers to send in the request token placement select whether to send the token in the header , query string, or both header token name enter the name of the authorization token in the header default bearer query string parameter name enter the name of the authorization token in the query string default access token module settings field description evaluate all states as errors (except for 2xx and 3xx) use the response status to detect errors otherwise, the module reports only {{product name}} related errors (like mapping errors or missing required values) url enter the request url serialize url encodes the api call url with the url encoding (encoding special characters for example) method select the http method you want to use get to retrieve information for an entry post to create a new entry put to update/replace an existing entry patch to make a partial entry update delete to delete an entry headers enter request headers for example, the response content type the http app requests do not have the accept header if the http request returns an unexpected response, try adding the accept / header query string enter the query key value pairs body type http body contains the data transferred in an http request the raw body type is suitable for most http requests, even if the app documentation does not specify the data type specify the data format of the body content in the content type field the application/x www form urlencoded body type is to post data using application/x www form urlencoded for application/x www form urlencoded , the body of the http request sent to the server is one query string the keys and values are encoded in key value pairs separated by & and with a = between the key and the value for binary data, use the multipart/form data body type instead example of the resulting http request format field1=value1\&field2=value2 use the multipart/form data content type to send files in the http request add fields to the request each field must contain a key value pair text enter the key and value to send in the request body file enter the key, and specify the source file you want to send in the request body map the file you want to upload from the previous module (for example http > get a file or google drive > download a file ), or enter the file name and file data manually parse response enable to parse http responses into bundles with this option, you don't need to add the parse json or parse xml modules otherwise, the http module returns the raw response data before you can use parsed json or xml content, run the module once manually so that the module can recognize the response content and allow you to map it in subsequent modules timeout specify the request timeout in seconds (1 300) default 40 seconds share cookies with other http modules enable to share cookies from the server with all http modules in your make self signed certificate upload your certificate if you want to use tls using your self signed certificate reject connections that use unverified (self signed) certificates enable to reject connections that use unverified tls certificates follow redirect enable to follow url redirects that return 3xx response statuses follow all redirect enable to follow url redirects regardless of response statuses disable serialization of multiple same query string keys as arrays make handles multiple values for the same url query string parameter key as arrays (e g , www test com?foo=bar\&foo=baz will be converted to www test com?foo\[0]=bar\&foo\[1]=baz ) enable to deactivate this behavior request compressed content enable to request compression of the response data adds the accept encoding header use mutual tls select if you want to use mutual tls (mtls) for the http request to ensure both the client and server authenticate each other using certificates make a request creates an http request and send it to a server the output bundle contains the http response this is a universal module, best to use for resources that do not require authentication field description evaluate all states as errors (except for 2xx and 3xx) use the response status to detect errors otherwise, the module reports only {{product name}} related errors (like mapping errors or missing required values) url enter the request url serialize url encodes the api call url with the url encoding (encoding special characters for example) method select the http method you want to use get to retrieve information for an entry post to create a new entry put to update/replace an existing entry patch to make a partial entry update delete to delete an entry headers enter request headers for example, the response content type the http app requests do not have the accept header if the http request returns an unexpected response, try adding the accept / header query string enter the query key value pairs body type http body contains the data transferred in an http request the raw body type is suitable for most http requests, even if the app documentation does not specify the data type specify the data format of the body content in the content type field the application/x www form urlencoded body type is to post data using application/x www form urlencoded for application/x www form urlencoded , the body of the http request sent to the server is one query string the keys and values are encoded in key value pairs separated by & and with a = between the key and the value for binary data, use the multipart/form data body type instead example of the resulting http request format field1=value1\&field2=value2 use the multipart/form data content type to send files in the http request add fields to the request each field must contain a key value pair text enter the key and value to send in the request body file enter the key, and specify the source file you want to send in the request body map the file you want to upload from the previous module (for example http > get a file or google drive > download a file ), or enter the file name and file data manually parse response enable to parse http responses into bundles with this option, you don't need to add the parse json or parse xml modules otherwise, the http module returns the raw response data before you can use parsed json or xml content, run the module once manually so that the module can recognize the response content and allow you to map it in subsequent modules user name enter the user name to send the request with the basic auth password enter the password to send the request with the basic auth timeout specify the request timeout in seconds (1 300) default 40 seconds share cookies with other http modules enable to share cookies from the server with all http modules in your make self signed certificate upload your certificate if you want to use tls using your self signed certificate reject connections that use unverified (self signed) certificates enable to reject connections that use unverified tls certificates follow redirect enable to follow url redirects that return 3xx response statuses follow all redirect enable to follow url redirects regardless of response statuses disable serialization of multiple same query string keys as arrays make handles multiple values for the same url query string parameter key as arrays (e g , www test com?foo=bar\&foo=baz will be converted to www test com?foo\[0]=bar\&foo\[1]=baz ) enable to deactivate this behavior request compressed content enable to request compression of the response data adds the accept encoding header use mutual tls select if you want to use mutual tls (mtls) for the http request to ensure both the client and server authenticate each other using certificates this is an example of how to set up the make a request module to send a post request with the body in the json data format to make sure your json is valid, use a json validator (for example https //jsonlint com/ ) or use a create json module to create the json be careful when combining json data with mapping variables or function directly in the request content field mixing json with mapping can lead to an invalid json structure resolve a target url gets a direct url to a resource instead of a redirect url for example, links for sharing files in storage apps like dropbox redirect you before you reach the target file the module navigates through the redirect chain and returns the target url enter the url you want to resolve the output bundle contains the link to which the original url redirects in the location response header field description url enter the url you want to resolve method select the method you want to use feeders retrieve headers returns each header (name and value) from the specified http module in a separate bundle field description source module select the module you want to retrieve headers from generate json web tokens (jwt) if you need to connect to an api or send messages that requires jwt authentication, you can create a jwt via the http module using the hs256 or hs512 algorithms make allows creating a jwt with the help of custom or built in functions generate a jwt with a custom function this feature is available to enterprise customers go to functions and create a custom function using the following body function readablejwtencode(payload, secret, header = '{"alg" "hs256","typ" "jwt"}') { let formattedheader = iml replace(iml replace(iml replace(iml base64(header), "=", ""), "+", " "), "/", " ") let formattedpayload = iml replace(iml replace(iml replace(iml base64(payload), "=", ""), "+", " "), "/", " ") let signature = iml sha256(formattedheader + " " + formattedpayload, "base64", secret) let formattedsignature = iml replace(iml replace(iml replace(signature, "=", ""), "+", " "), "/", " ") let jwt = formattedheader + " " + formattedpayload + " " + formattedsignature return jwt } replace hs256 with hs512 and sha256 with sha512 in the custom function above to create a hs512 jwt the example custom function has the jwtencode name embedded onto the function body if you want to use another name, change it in the body too start your {{scenario singular lowercase}} with the set multiple variables module and add the following field value item 1 variable name header item 1 variable value {"alg" "hs256","typ" "jwt"} replace hs256 with hs512 to create a hs512 jwt item 2 variable name payload item 2 variable value {"var1" 1,"var2" "text"} item 3 varible name secret item 3 variable value enter your 256 bit or 512 bit secret add another set multiple variables module to generate the jwt optional in variable name , enter the name for the token in variable value , enter the following function {{jwtencode(11 payload; 11 secret)}} make sure to take into account the module number in the code in the example above, the header, payload and secret are in the 11th module in the {{scenario singular lowercase}} it may vary from one {{scenario singular lowercase}} to another if you run the {{scenario singular lowercase}} , you will receive the hs256 or hs512 jwt in the second module's output you can connect to an api or send messages that requires jwt authentication generate a jwt with built in functions start your {{scenario singular lowercase}} with the set multiple variables module and add the following field value item 1 variable name header item 1 variable value {"alg" "hs256","typ" "jwt"} replace hs256 with hs512 to create a hs512 jwt item 2 variable name payload item 2 variable value {"var1" 1,"var2" "text"} item 3 varible name secret item 3 variable value enter your 256 bit or 512 bit secret add another set multiple variables module to generate the hs256 or hs512 jwt optional in variable name , enter the name for the token in variable value , enter the following function {{5 header}} {{5 payload}} {{replace(replace(replace(sha256(5 header + " " + 5 payload; "base64"; 5 secret); "="; emptystring); "+"; " "); "/"; " ")}} use the sha512 function to create a hs512 jwt make sure to take into account the module number in the code in the example above, the header, payload and secret are in the 5th module in the {{scenario singular lowercase}} it may vary from one {{scenario singular lowercase}} to another if you run the {{scenario singular lowercase}} , you will receive the hs256 or hs512 jwt in the second module's output you can connect to an api or send messages that requires jwt authentication