Real-Time Attendance Machine Integration with Pabbly Connect

Our requirement is that whenever an employee marks attendance on the machine (IN/OUT), the attendance data should be automatically sent to Pabbly Connect in real time through a webhook/API.

The required data includes:

• Employee ID
• Employee Name
• Date
• Punch/Attendance Time
• IN/OUT Status

Please guide us on:

1. Whether Pabbly Connect can directly receive data from a biometric attendance machine.
2. What API/Webhook format is required.
3. How we can configure the machine/software to send attendance data to Pabbly.
4. Whether any middleware or attendance software/API is required between the machine and Pabbly Connect.
5. Please provide the complete setup procedure and any required API/webhook documentation.

Hello,

Thank you for reaching out.

Whether Pabbly Connect can receive data from your biometric attendance machine depends on how the machine (or its accompanying software) can send data out. Here is how it works:

1. Direct data reception: Pabbly Connect can receive attendance data in real time, but only if your machine or its software can send outbound webhooks (an HTTP POST request) or exposes an API. Pabbly Connect cannot connect to a device that has no webhook or API support.

2. Recommended method (Webhook): If your attendance machine/software supports outbound webhooks, use the Webhook by Pabbly trigger:
   - Create a new workflow in Pabbly Connect and select Webhook by Pabbly as the trigger.
   - Copy the unique webhook URL that Pabbly generates.
   - Configure your machine/software to send an HTTP POST request to that URL whenever an IN/OUT punch occurs.
   - Send the payload in JSON format with clear key/value pairs, for example: employeeid, employeename, date, punchtime, inout_status.
   - Trigger one test punch so Pabbly Connect can capture the payload structure.
   - Add your subsequent action steps and map the captured fields into them.

3. Format: JSON is the recommended payload format, sent over HTTPS. Treat the webhook URL as a secret. No special authentication setup is required from your side, as the webhook URL itself acts as the endpoint identifier.

4. If the machine cannot send webhooks but exposes an API, you can alternatively use the API by Pabbly / HTTP request action to pull data on a schedule, though webhook (push) is preferred for real-time use cases.

Could you please confirm whether your biometric machine or its software supports outbound webhooks or provides an API? Once we know that, we can guide you on the exact setup.