Run a pipeline on a request, with no account.
Pick a sample, change the pipeline or the request, and see what comes out: the body and headers it would send, the step that dropped it, or why it failed. It runs on the same engine as Transforms, on our servers, and saves nothing.
Unlike the tools that run in your browser, this one sends the pipeline and the request to our servers, because that is where the engine runs. They are used for that one run and then discarded: nothing is saved and neither is logged. Your address counts toward the rate limit. Use sample data here, not real credentials or personal data.
The engine Transforms runs, with smaller caps.
A pipeline here behaves as it does in the product, so what you learn carries over. The differences are that nothing is saved, that a run has less room, and that the slot a credential step names isn’t checked, while the product takes only a slot the workspace holds.
Transforms, Webhooks and Request Bins all run pipelines on this one engine, so what a document does here is what it does there.
Filter, remove fields, set fields, reshape the body, headers and credentials, with every filter in the template language.
A credential step runs on a placeholder, not on any real value, and shows as Bearer ••••, as it does in Test and the run API.
A 16 KiB document, a 32 KiB body and 10,000 values read or copied in a run, where the product allows 64 KiB, 256 KiB and 100,000.
Three things to change in the samples.
In the paid invoices sample, lower the amount in the request below 100000 and run it again. The result names the step that dropped it, with its note.
The Slack sample builds the body a Slack incoming webhook takes. Change the event’s type or data and see the message change, cut to fit Slack’s limits.
The personal data sample removes fields at any depth. Add a path of your own to the list, or nest an email deeper in the request, and see what stays.
About the playground.
No. The pipeline and the request go to our servers for that one run and are then discarded, and neither is written to a log. Use sample data all the same: this page has no need of real credentials or personal data.
Because Transforms never shows a credential, and here there isn’t one. A credential step runs on a placeholder, so you can see which header or query parameter it would set. To send a real credential, a product runs the pipeline by reference and fills the slot from its own secrets.
20 a minute from one address, with up to 10 at once. Past that the page asks you to wait a moment. On an account, Free allows 60 a minute.
It doesn’t save anything, so there are no versions and no run API, and a product can’t refer to what you built here. A run also has smaller caps: a 16 KiB document and a 32 KiB body.
Sign up, create a pipeline in the console and paste the document in. A credential step first needs a slot made in the console, whose id replaces sec_demo, and an owner or admin to save the pipeline. Free includes 5 pipelines, every step and every template.
Save it, version it, and run it from your own code.
Free includes 5 pipelines, every step and every template, and 60 runs a minute.