Send automated HTTP requests (GET, POST, PUT, DELETE) from within a workflow job to external systems such as MIS, REST APIs, or notification services.
| Field | Description |
|---|---|
| URL | The destination endpoint. Supports variable placeholders (see below). |
| Method | HTTP verb: GET, POST, PUT, or DELETE. |
| Headers | Optional key/value pairs such as Content-Type. A default header is automatically added based on your selected content type (JSON, XML, or Text). |
| Body | For POST and PUT methods, the payload sent in the request. Can include placeholders like {JobName} or {DateTime}. |
You can include dynamic variables in the URL, headers, or body. These are replaced at runtime based on the job’s properties.
| Placeholder | Meaning |
|---|---|
{JobName} | Current job’s name. |
{DocumentName} | First document’s name in the job. |
{Barcode} | Job barcode, auto-generated if not present. |
{DateTime} | Current local date and time (YYYY-MM-DD HH:MM:SS). |
{JobGuid} | Job’s unique GUID. |
{MediaType} | Media type value from job settings. |
{MediaSize} | Media size or sheet format name. |
{PrintDeadline} | Earliest deadline among all parts. |
{Key:YourKey} | Any custom key defined in the workflow. |
Method: POST
URL: https://api.example.com/job/update?barcode={Barcode}
Headers:
Content-Type: application/json;charset=UTF-8
Body:
{
"jobName": "{JobName}",
"guid": "{JobGuid}",
"deadline": "{PrintDeadline}",
"media": "{MediaType}"
}
GET first before enabling POST payloads.Authorization: Bearer {Key:Token}.