Figgo offers a module for real-time synchronisation with an external tool, allowing you send leaves and absences to:
- an Outlook calendar or Google Calendar (for GSuite clients)
- payroll solutions
- another third-party tool (schedule, for example), using a generic connector
Synchronisation is a service. For more information regarding an estimate, please contact the Lucca help desk
Possible synchronisation types:
Synchronisation with a calendar
We can automatically send leaves and absences to the employees’ calendar for the following solutions:
- Outlook with Office365
- Outlook with an Exchange server
- Google Calendar (G Suite Client)
We do not offer synchronisation with a single shared calendar or synchronisation to personal Google account calendars.
Synchronisation with Slack
Synchronisation with Slack allows you to post the days’ absences on the channel of your choice.
Synchronisation with payroll solutions
We can explore development of connectors for payroll solutions offering web services or API, allowing real-time creation or deletion of absences. Contact us for more information.
We can now synchronise absences with ADP GXP payroll services in real-time.
Synchronisation with a third-party tool
Our generic connector (called HTTP Synchronisation) allows you to send real-time absence creations or deletions in a third-party tool with no dedicated connector.
This page describes how it works.
Synchronisation management module
Figgo offers a module dedicated to configuring and tracking absence synchronisation.
Module access rights are granted using two permissions available in the Figgo application roles:
- View synchronisations: allows you to see synchronised events, their status (successful, error) and manually re-sync them if needed.
- Configure synchronisations: viewing rights, with access to sync set-up (URL, service account, entities, etc.).
The event follow-up interface allows you to view all events sent to the third-party service in real time using the web service. The status is indicated for each event (Pending, Successful or Error). You can view event details, including the payload and responses from the external service, so problems can be identified more easily.
The synchronisation web service has an automatic re-sync policy if the call fails. The failed event is then queued for re-syncing. There are 4 successive queues at: 5 minutes, 15 minutes, 1 hour, 24 hours.
You can manually re-sync a failed event (Retry button) or change the status to ‘successful’ if it was manually entered into the third-party tool, for example (Mark as processed button).