Thanks to conditional actions in Uspacy, you can automate the launch of the vacation approval process—for example, after an employee submits a request. This reduces the number of manual actions, ensures a transparent approval sequence, and speeds up decision-making.

Let’s take a look at how you can set up such automation so that the process is clear, timely, and doesn't require constant reminders.

In this example, we will be working with a custom Smart Object called “Vacations.”

Thus, when any employee creates a new vacation request in the system, it will automatically trigger the processing mechanism. First comes the initial approval—for example, by an HR or accounting staff member. Then, after that approval, comes final confirmation—typically by the direct manager. After that, the result is shown to the employee: Approved or Rejected.

Step by step instruction below ⬇️

First, select the trigger. In our example, it is the creation of a Smart Object — Vacations.

Next, define the action — specifically, Change fields.

Then, specify that for this Smart Object (i.e., the vacation request), after creation, the system should change the title to a standardized format + include the system ID, and assign another person as responsible.

Finally, create this conditional action.

After the employee creates a new vacation request, the system will automatically update the title and assign a new person responsible to review and approve the request.

First, select the trigger. In this case, it's a stage change for the vacation request.

As a condition, select the transition to the Approved stage (from the Approval direction).

Next, define the action — Change fields.

Specify that once the request moves to the Approved stage, it will be transferred to another direction — Confirmation, and to the stage For approval.

If other fields also need to be updated or filled, add a separate action for that.

For example, specify who is now responsible for the next confirmation step and who previously approved the leave request and when.

Then create the conditional action.

The person responsible for approval makes a positive decision.

After refreshing the page, you’ll see the conditional action in effect:

The vacation request moves to a new stage and direction, a new responsible person is assigned, and the card now includes info about the prior approval (date and user).

First, select the trigger — in this case, a stage change for the vacation request.

As a condition, select the transition to the Approved stage (from the Confirmation direction).

Then, define the action — Change fields.

Indicate that the responsible person should now be the one who originally created the vacation request. Also note who and when gave the final approval.

Next, add a separate Comment action.

Write the comment text that will appear in the vacation request card as a note, if the approval is successful.

Finally, create the conditional action.

The person responsible approves the vacation request.

After refreshing the page, you’ll see the conditional action in effect:

Responsibility returns to the employee who initiated the request, and the card now includes info about the final approval (date and user), along with a note about the positive outcome.

Again, start by selecting the trigger — a stage change for the vacation request.

As a condition, select the transition to the Rejected stage (from the Confirmation direction).

Then define the action — Change fields.

Specify that the person responsible should now again be the employee who created the vacation request. Also record who and when made the final decision to reject.

Next, add a Comment action.

Write the comment that will appear in the vacation request card as a note if the confirmation ends with a negative result.

Finally, create the conditional action.

The person responsible rejects the vacation request.

After refreshing the page, you’ll see the conditional action in effect:

The original requester is once again marked as responsible, and the card now includes info about the final decision (date and user), along with a note indicating that the request was rejected.

If you have additional questions or you need to contact the support, send a request to this email [email protected]