Overview
Automations can drive a huge variety of outcomes, from a simple notification to a full integration with a third party system. Today, automations act by sending a webhook to another service, which can pass the event details on to almost anything. Unless the destination can be configured to accept FUYL.io's specific data format directly, an organization may need a workflow automation tool to (at a minimum) “translate” the data so it is usable, or to apply further logic and couple multiple additional actions together.
The examples below are a starting point for inspiration. Each notes the trigger it responds to and the fields it relies on; for the exact payload of each event, see Webhooks (technical reference). For how to build an automation, see Automations.
Remind users about loans due back, in the organization's own style
Trigger an automation on the purpose-built loan.reminder event (or on loan.created / loan.overdue) and point it at the organization's own email platform or messaging tenant. The payload includes the user's name and email, the device ID, and the expectedReturnDateTime, so reminders can be sent from a familiar address, in the organization's own branding and terminology. This is a good option where messages need to match the organization's voice, or to route them through a system that is already trusted by its users.
Open a pre-filled repair ticket
Trigger on repair.user_dropoff and send the webhook to the service desk or ticketing system's intake endpoint. The payload carries the deviceId, the reporting user, the site and kiosk, and the dropoffReason (type and description). The ticketing system may use these to create a ticket with the correct fields prefilled, or even route the ticket to the appropriate supporting agent for a quicker response.
Ping a local admin on Teams when a locker goes offline
Trigger on the Offline station event and point the webhook at an incoming webhook URL for a Microsoft Teams (or Slack) channel. As soon as a locker drops offline (power outage, cable disconnected etc), the responsible site admin gets a proactive message, avoiding interruption for the next user. Add a Site condition to send each location's alerts to the right team.
Flag low stock before it runs out
Trigger on deployment.devices_low (or No loan devices) and send the webhook to a chat channel, an email list, or a procurement workflow. The payload includes the threshold and numAvailableDevices, so the right people are prompted to restock a site before users are left without an available device.
Where to go next
Build your own automation:
Automations - What automations are, and how to create and manage them.
Automation Actions - Webhooks - How to configure the webhook action, how to receive one with a workflow automation tool, and the full list of events and their respective payload formats.