Base44: Connector Webhook Triggers for Backend Functions
Base44Base44 now allows backend functions to trigger automatically in response to real-time webhook events from connected services, including Gmail, Google Calendar, Google Drive, Microsoft Outlook, Microsoft OneDrive, Slack, Microsoft Teams, and SharePoint. Developers configure these event-driven triggers directly in function.jsonc alongside existing scheduled and database automations, with optional filter conditions to target specific event types. This closes a key gap for teams building reactive, event-driven integrations — removing the need for polling or external orchestration tools like Zapier. The feature significantly expands what developers can automate within Base44-hosted backend functions.
Featured Video
A video we selected to help illustrate this changelog
Sources & Mentions
5 external resources covering this update
Connector Webhook Triggers for Backend Functions
Base44 has extended its backend function automation system to support real-time webhook triggers from connected external services. As of April 28, 2026, developers can configure backend functions to execute automatically whenever a supported integration fires an event — without writing custom webhook handlers or relying on third-party automation layers.
How It Works
Connector automations are configured inside a function's function.jsonc file, the same place where scheduled jobs and database event triggers are defined. A trigger entry specifies which connector and event type should fire the function, and an optional conditions block lets developers filter events so only relevant ones trigger execution.
When an event fires — say, a new email arriving in Gmail or a file change in Google Drive — Base44 routes the webhook payload to the corresponding backend function automatically. The function receives the full webhook payload as its input, giving developers access to all event data for processing.
Supported Services and Events
The April 28 release enables connector automations across the following services:
- Gmail — triggers on new incoming emails
- Google Calendar — triggers on calendar event creation, updates, and deletion
- Google Drive — triggers on file additions, modifications, deletions, and trash operations
- Microsoft Outlook — triggers on email, calendar, and contact changes
- Microsoft OneDrive — triggers on file and folder changes
- Slack — triggers on incoming Slack events
- Microsoft Teams — triggers on Teams activity
- SharePoint — triggers on SharePoint content events
Base44's documentation covers the full event table, trigger condition syntax, webhook payload structure, and working code examples.
Why This Matters
Previously, reacting to external events in a Base44 app required either polling an API on a schedule (inefficient and delayed) or setting up an external webhook relay through tools like Zapier. With native connector automations, developers can build event-driven workflows entirely within Base44 — a new email triggers a database write, a calendar update fires a notification, or a file change kicks off an AI processing pipeline — all managed in the same codebase as the rest of the app.
Prerequisites
The relevant connector must be connected and configured in the app's Integrations dashboard before a connector automation can be attached to a backend function. Trigger conditions are optional but recommended to avoid processing irrelevant events.