Scheduled CRM exports to SharePoint
Initiate scheduled CRM report exports, download them, and replace the files in the shared folders.
Overview
CRM reports need to be available as files in shared folders. In the evening, this automation triggers the configured exports. In the morning, it downloads them and replaces the old files in the appropriate SharePoint folders after clearing the local download folder. Errors are emailed with a screenshot.
What has changed
- Reduced manual file handling
- No outdated files in shared folders
- Logs and error messages ensure traceability
At a glance
In één oogopslag
Overzicht
CRM reports need to be available as files in shared folders. In the evening, this automation triggers the configured exports. In the morning, it downloads them and replaces the old files in the appropriate SharePoint folders after clearing the local download folder. Errors are emailed with a screenshot.
Wat er verandert
- Reduced manual file handling
- No outdated files in shared folders
- Logs and error messages ensure traceability
How it works.
the folders
What it does per export
- Start the configured exports in the CRM reporting portal
- Collects the export links
- Opens each link and waits for the export to complete
- Downloads the file and checks the download folder
- Deletes the old file in the appropriate SharePoint folder
- Uploads the new file and confirms the action
Rules
A file is only downloaded to an empty folder, and the export type determines which SharePoint folder the file goes to, with the old file being deleted first. Failed exports are checked before downloading. Because the logic is fixed, the same input always yields the same result, and every run is logged.
Check out other automations.
Frequently asked questions.
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.
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.
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.
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.
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.