Send HTTP request is an action that sends a request to a web address when your automation runs and saves the response in a variable. In the action list, its description reads Send an HTTP request and save the response in a variable for later use. It's meant to help you connect Tape to any service that has a web interface (an API), without a script.
You can use this action for many things, including:
Sending a new customer to your accounting system when a deal is won.
Asking a service for the current exchange rate and using it in a quote.
Note:
Only public addresses. Tape refuses requests to private or internal addresses, such as
localhostor hosts inside a private network. This protection is always on.No login included. This action doesn't sign requests. For a service that needs an OAuth 2.0 login, use
Send API request. Learn more about Send API request →Requests send real data. A manual run sends real requests to the service. Test with a service that has a test mode.
Who can use the Send HTTP request action?
Automations are available on the Free, Plus, and Premium plans. The number of automation actions per month depends on your plan. See the limits for your plan on our pricing page.
To add or change this action, you need to be a workspace admin of the workspace the app is in. You also need full access to every app the automation uses.
Add the Send HTTP request action
To send an HTTP request from an automation:
Open the database app and click the automations icon in the top bar (tooltip
Create and view automations). The icon is only there for workspace admins, and not on mobile.Open an automation, or select
New automationand choose a trigger.Select
Add action→Send HTTP request. The step appears asSend a HTTP request.Select the method next to
using. It starts asGET.Enter the address in
URL.Add the data to send in
Request. Type@to insert record values.Select
Show headersif the service needs headers.Select
Create automationfor a new automation, orSave changesfor an existing one.
Send HTTP request settings
The action reads as a sentence: Send a HTTP request using GET method and save response in HTTP response. Below, you'll see:
The method: how the request is sent. Select it to choose:
GETasks the service for data.POSTsends data, usually to create something.PUTsends data to replace something.PATCHsends data to change part of something.DELETEasks the service to delete something.HTTP response: the name of the variable that holds the response, afterand save response in. You can use it in later actions by typing@. You can rename it when you send more than one request. It holds the body of the answer, without the status code or headers.URL: the address the request goes to. You can mix text with record values, for examplehttps://api.acme.com/customers/followed by the record's ID.Request: the content that is sent along, for example text in JSON format. You can mix text with record values.Requestis sent with every method if it isn't empty. Add URL parameters directly to theURL, for example?status=open.Show headers: opens the list of headers. SelectAdd headerto add one, then fill inHeader(the name, such asContent-Type) andValue(such asapplication/json). SelectHide headersto close the list. Values can contain record values.Follow redirects: in the action's•••menu. When it's on, the request follows redirects of the service to the new address. It's off by default.
Use the response in later actions
The response is saved in the variable named after and save response in. In a later action, type @ and select the variable, for example to write a value into a field with Update record, or add it to an email.
The variable holds the body of the response. If the service marks its answer as JSON (
Content-Type: application/json), it's saved as an object, and you can read single values withPerform calculationorExecute script, for examplevar_http_response.id. Learn more about Execute script →If a request has to finish before the next step, add the next action below it. Actions run from top to bottom, one after the other.
Let's look at an example
Let's say your sales team wants every won deal to create a customer in your accounting system. Here's how:
Set the trigger to
When a record is updatedand select the fieldStage.Add the filter
WhereStageHas changed to"Won".Select
Add action→Send HTTP request.Set the method to
POSTand enterhttps://api.acme.com/customersinURL.Select
Show headers→Add header. EnterContent-TypeasHeaderandapplication/jsonasValue.In
Request, write the customer data in JSON format and insert the deal'sCompanyandEmailfields at the right places.Select
Create automation.
The next time a deal is won, Tape sends the customer to the accounting system and saves the answer in HTTP response.
Send HTTP request errors
If the step fails, the run shows the step and its message in the automation's runs. Open the automation and click
▷(View all runs) at the top, or usecmd/ctrl+1. Each run shows its status, for exampleSuccess; select a run to see every step. For all automations, openRunsin the Automation Center and filter byApp,Automation, orStatus.An error status like 404 or 500 doesn't fail the step. Only errors that stop the request do, for example an address that can't be reached. The response variable holds only the body of the answer, so check it in a later step.
If the address points to a private or internal host, the request is refused.
If the service blocks unknown servers, allow Tape's IP addresses. Learn more about IP addresses →
If the service doesn't answer, the run ends after three minutes at the latest. Learn more about limits →
Test, pause, or edit the Send HTTP request action
Manual runruns the automation once. UnderRun on, select the records, then selectStart run, orSave and start runif you have unsaved changes. The requests go to the real service.New automations you create in the editor are
Activeright away. The status,ActiveorPaused, sits right below the automation's name in the editor. To pause one, selectActive, then selectSave changes. The status switches toPaused.To change the action, open the automation, select the
Send a HTTP requeststep, make your changes, then selectSave changes.
Learn more
FAQs
Which methods can I use?
Which methods can I use?
GET, POST, PUT, PATCH, and DELETE.
How do I send data to a service?
How do I send data to a service?
Set the method to POST, PUT, or PATCH, enter the address in URL, and write the data in Request. If the service expects JSON, add the header Content-Type with the value application/json.
Can I use the response?
Can I use the response?
Yes! The response is saved in the variable after and save response in. Type @ in a later action and select it. Learn more about record values and variables →
Can I call a service that needs a login?
Can I call a service that needs a login?
If the service uses OAuth 2.0, use Send API request and select a connection. If it uses a key, add the key as a header. The key is saved in the automation, and everyone who can edit the automation can see it. Use a key that only has the rights the automation needs. Learn more about Send API request →
Can I send files or upload an image from a URL?
Can I send files or upload an image from a URL?
No. Request only sends text. To send a file, use http.upload in Execute script. Learn more about Execute script →
Which IP addresses does Tape use?
Which IP addresses does Tape use?
Requests come from a small set of fixed addresses, which can change. Learn more about IP addresses →
Can I call a service in my own network?
Can I call a service in my own network?
No. Tape only sends requests to public addresses. Requests to private, internal, and local addresses are refused.
Are there other actions I can use?
Are there other actions I can use?
Yes! Actions can create and update records, add comments, send emails, create PDFs, call other services, and more. See every action in Automation actions →
Are you a developer using the Tape API for automations?
Are you a developer using the Tape API for automations?
The automation API has its own documentation for developers. Full reference: http_call in the developer docs →
Still have questions? Find answers and get help from community experts in the Tape community →
