Automation library
>
IT and HR
>
Youforce export to central storage

Youforce export to central storage

Downloads the daily HR or payroll export from Youforce and places it in central storage.

Overview

The daily HR or payroll export in Youforce needs to be moved to central storage. This automation logs in, locates the day's export, downloads and unzips it, uploads the files to blob storage, and retries the login a limited number of times.

What has changed

  • Eliminates a repetitive download-and-upload task
  • Reduced risk of missing files
  • Data arrives in central storage in the same way every day

At a glance

SECTOR:
ISV
System:
Youforce, Azure Blob Storage
RUNS:
Daily at 04:31
Technique:
Rule-based

In één oogopslag

SECTOR:
ISV
Systeem:
Youforce, Azure Blob Storage
RUNS:
Daily at 04:31
Techniek:
Rule-based

Overzicht

The daily HR or payroll export in Youforce needs to be moved to central storage. This automation logs in, locates the day's export, downloads and unzips it, uploads the files to blob storage, and retries the login a limited number of times.

Wat er verandert

  • Eliminates a repetitive download-and-upload task
  • Reduced risk of missing files
  • Data arrives in central storage in the same way every day

How it works.

Youforce daily export
Logindone
Today's file namedone
Download ZIPrunning
Retry limit in place
04:31 every day
Y
Yara unzips
and uploads
Central storage azure blob storage
employees.csvuploaded
payroll.csvuploaded
contracts.csvuploaded
Ready for other systems
Always the right export, picked by date.

What it does per run

  1. Logs in to Youforce, with a limit on retry attempts
  2. Constructs the expected filename based on the current date
  3. Filters the file list and selects the correct export
  4. Downloads the ZIP file
  5. Unzips it
  6. Uploads the files to blob storage

Rules

The filename is constructed from the current date, and the login is retried up to three times. The same input always leads to the same outcome, and every run leaves a log that can be audited.

Frequently asked questions.

Do we need to change our system?

No. The digital colleague works in the screens and systems your team already uses, whether they are legacy applications without an API or modern ones, so there is nothing to replace.

Who builds and maintains the automation?

Yarado builds it, runs it and monitors it. When a screen or a system changes, we adjust the automation, so your team needs no developer or automation skills of its own.

Can we see what it did?

Yes. Every run is recorded in the Yarado portal, where you can see which processes ran, when they last ran, what they produced and what went wrong. Depending on the automation, the processing log is also emailed to the team that needs it.

What happens if something goes wrong?

Yarado monitors every run and is alerted automatically when one fails, so a problem is picked up on our side. Cases that need a person are reported to your team with the reason, in the portal or by email.

Can it work for our process, even if it differs from this example?

Yes. Automations are built around your own steps and systems, and this page is just one example of what is possible. A first automation is typically live in weeks, not months.

Process not found?

Don't see your process listed? Let us know. We'll start with an automation scan to see what can be automated.