docs/guides.mdx
Novu provides various ways to integrate with external services to trigger notification workflows. Here are the main integration approaches:
Webhooks enable real-time event-driven communication between applications, making integrations more efficient and responsive.
In Novu, webhooks trigger notification workflows whenever specific events occur in external applications. This ensures notifications are delivered exactly when they're needed, keeping users informed without delay.
For example, when a user signs up via Clerk or completes a payment through Stripe, a webhook delivers the event payload to Novu, which then processes it and triggers the appropriate workflow.
This allows for real-time notifications—whether it's a welcome email, payment confirmation SMS, or in-app alert—without the need for constant polling, ensuring efficiency and a seamless user experience.
<Columns cols={2}> <Card title="Clerk" icon="/images/icons/clerk.svg" href="/guides/webhooks/clerk"> <p> Use Clerks webhooks events to trigger authentication related notifications workflows. </p> </Card> <Card title="Auth0" icon="key" href="/guides/webhooks/auth0"> <p> Trigger Novu workflows from Auth0 signup, password reset, and security events. </p> </Card> <Card title="Stripe" icon="/images/icons/stripe.svg" href="/guides/webhooks/stripe"> <p> Use Stripe webhooks events to trigger payment related notifications workflows. </p> </Card> </Columns>Some integrations use different mechanisms than webhooks to send data to Novu. For example, analytics and data platforms often use custom destinations or functions to forward events.
<Columns cols={2}> <Card title="Segment" icon="activity" href="/guides/webhooks/segment"> <p> Use Segment's Destination Functions to forward user events and traits to trigger notification workflows. </p> </Card> </Columns>Workflow automation platforms help orchestrate complex business processes and event-driven workflows. Integrating Novu with these platforms allows you to trigger notifications as part of your automated workflows.
<Columns cols={2}> <Card title="Inngest" href="/guides/inngest"> <p> Use Inngest's event-driven workflows to trigger notifications at specific steps in your automation pipeline. </p> </Card> <Card title="Trigger.dev" href="/guides/triggerdotdev"> <p> Leverage Trigger.dev's developer-friendly workflow engine to send notifications based on scheduled or event-driven triggers. </p> </Card> </Columns>