Incoming JUnit File webhook
Receive a JSON submission from your existing form backend at this Workflow's private webhook URL.
→
Ready-made Workflow
Import a JUnit File into Katalon from a webhook
Import one JUnit XML report through Katalon’s official allocate, binary upload and registration flow. Connect Katalon on all three Actions, enter the same numeric project ID in Allocate upload URL and Register JUnit report, and enter a report folder path in Register JUnit report. Send a FastHook File as file plus a fresh globally unique batch string. The example File is a fictional passing test, not a real test execution. The upload is raw PUT to Katalon-allocated signed storage, with no API key sent to storage. Files are limited to 25 MiB. Registration returns 204; parsing happens asynchronously and must be checked in Katalon Executions. Do not reuse the batch across projects or report types. Protect the source URL and check existing imports before rerunning uncertain submissions. New tenant accounts need the legacy CI import API entitlement.
Use this templateCreates a new Draft · no credentials copied
What gets copied
The working graph, not another user's secrets
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Allocate upload URL
Allocates fresh upload destinations for a project. The response is a JSON array of file metadata. Each `uploadUrl` is a private, signed PUT capability; keep it out of logs and use it only for the indicated PUT. Do not send your API key to the signed destination. Access to the requested project is checked. Choose a small positive `numberUrl`, such as `1`. The maximum is not documented. A non-positive count returns an empty array. GET /api/v1/files/upload-urls
Upload JUnit File
Upload one File (up to 25 MiB) to the full presigned HTTPS URL allocated by Katalon. No API key is forwarded to storage. Register the uploaded path with the corresponding import or attachment action afterwards.
Register JUnit report
Registers one JUnit report file after you PUT its bytes to a signed upload destination. Send no request body. Repeat this request for each file in the batch. Use one fresh `batch` value for the intended import, and keep the same project and Basic-auth credentials for every file. The project ID is a decimal string that the server parses as a long. Send `isEnd=true` only on the final registration after every file PUT succeeds. A fresh JUnit batch without `sessionId` is intended to group its XML files into one test run. Reusing a `sessionId` can join batches to an existing test run, so batch count does not guarantee run count. The parser reads files with whitespace-free names that end in `.xml`. It supports a `<testsuite>` or `<testsuites>` root. A successful `204` only confirms registration; parsing is asynchronous and the response has no run ID. A repeated final request without `sessionId` can create another test run. The batch key does not make this route safe to replay. `pushToXray=true` requests an Xray push. `false` or an omitted value does not prevent a push when the test run's policy allows one. POST /api/v1/junit/test-reports
Before activation
Connect your accounts in the Draft
Webhook
Send JSON submissions from your existing backend to the private webhook URL created in your Draft. No Webhook account is needed.
Katalon
Connect your own Katalon account and review the provider settings used by this Workflow.
Explore connected apps
Related Workflow templates
Webhook · Katalon
Create a Katalon manual test case from a webhook
Create one manual test case from incoming JSON containing name, description and a steps array with description/expectedResult fields. Connect Katalon, set Repository ID to a writable Cloud repository, and set Folder path to an existing test-case folder rawPath. Find these with Search test repositories and Search test folders; a repository ID is different from the default project ID. Protect the incoming webhook before activation. The template creates a manual test asset and does not run tests. Only new requests after activation are processed. Repeated requests and manual reruns can create additional cases; inspect Katalon before retrying an uncertain creation. The example is fictional.
- 1. Webhook · Incoming test-case webhook
- 2. Katalon · Create manual test case
Questions
Template FAQ
Does the template copy someone else's credentials?
No. FastHook creates a disconnected Draft. Connect your own Katalon accounts before activation.
Can I change the Steps and mappings?
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
What is copied into my workspace?
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
When does the Workflow start running?
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.