Skip to main content
Webhooks allow you to receive real-time notifications from absentify whenever specific events occur, such as when a request is created, its status is updated, or when users are created or modified. This enables seamless integration with your internal tools or external systems.

​
Network requirements

If your webhook endpoint is behind a firewall, allowlist the following IP address so absentify can send webhook notifications: Outbound IP address: 4.231.227.89 All webhook HTTP POST requests from absentify originate from this IP address.

​
What are webhooks?

A webhook is a method for apps to send real-time information to other apps. In the context of absentify, webhooks allow your systems to listen for specific events (e.g., leave requests being created, user accounts being updated) and respond immediately by triggering workflows or automating processes.
For technical details on implementing webhooks, visit our Developer Documentation.

​
Benefits of webhooks

  • Real-time updates: Receive instant notifications about changes in absentify, such as new leave requests, status updates, or user account changes.
  • Seamless integration: Connect absentify with your internal systems, such as HR software or notification tools.
  • Custom workflows: Use webhooks to trigger automated actions, such as sending notifications, updating dashboards, or integrating with custom tools.

​
Setting up webhooks in absentify

​
Step 1: Access the webhook settings

  1. Go to Settings > Integrations.
  2. In the Webhooks section, select Configure URL(s).

​
Step 2: Add a webhook URL

  1. In the URLs for receiving webhooks section:
    • Select the event you want to listen to:
      • All requests: Receive notifications when requests are created or their status changes
      • Request Created: When a new absence request is submitted
      • Request Status Changed: When a request is approved, denied, canceled, or modified
      • User Created: When a new user is added to the system
      • User Updated: When user information is modified (profile, role, etc.)
      • All users: Receive notifications when users are created or updated
    • Enter your endpoint URL in the text box (e.g., https://your-webhook-endpoint.com).
  2. Select Add to save the webhook.
You can add up to 3 webhook endpoints to receive notifications for different events.

​
Payload format

All webhooks configured through the UI use the v1 payload format. Request events are sent as a flat JSON object with an event_type field at the root; user events use an event_type and body wrapper. For the complete field reference and example payloads, see the Developer Documentation.
Use the event_type field to distinguish between events. For request status details, also check details.status and cancellation fields (canceld_date, cancel_reason).

​
Step 3: Manage existing webhooks

  1. You will see a list of configured webhook URLs under URLs for receiving webhooks.
  2. For each webhook, you can:
    • Edit the URL or event type using the pencil icon.
    • Delete a webhook using the trash icon.

​
Step 4: View webhook history

  1. At the bottom of the webhook settings, select Notification log.
  2. This displays a history of all webhook events, including:
    • The status of each event (e.g., “SUCCESS”).
    • The event name (e.g., “Request created”, “User updated”).
    • The number of delivery attempts.
  3. Use the Retry button to resend any failed webhook deliveries.

​
Using webhooks with Power Automate

Webhooks are a no-code way to trigger Power Automate flows from absentify, without the absentify connector. The flow exposes a public URL via the When a HTTP request is received trigger; you register that URL here as the webhook endpoint. This is the recommended Inbound path when:
  • The absentify connector is not yet available in your tenant.
  • You want event-driven automation but cannot or do not want to use the connector.
  • You want to combine event reception with direct API calls in the same flow.
Step-by-step guide: Power Automate (HTTP & webhooks).

​
Example use cases for webhooks

​
Request-based workflows

  • Notifications: Send notifications to Slack or Microsoft Teams when a new leave request is created.
  • HR automation: Automatically update records in your HR management system when a request’s status changes.
  • Dashboards: Update real-time dashboards with the latest absence data.

​
User management workflows

  • Onboarding automation: Trigger welcome emails or account setup processes when a new user is created.
  • Directory synchronization: Keep external user directories in sync when user information is updated.
  • Access management: Automatically provision or update user access in connected systems.

​
Advanced usage and developer support

To build custom integrations or handle advanced webhook workflows, refer to our Developer Documentation. It provides detailed information about:
  • Available webhook events.
  • Current v1 payload structure for request and user events.
  • Planned v2 format (Public API aligned).
  • Best practices for securing your webhook endpoints.
You can also use the Microsoft sync logs to monitor events triggered by connected Microsoft services or automated sync operations.
If you need help or have questions about webhooks, contact our support team or consult our developer resources.