- You only need simple, one-off API calls that complete within a single request. In that case, a direct Supabase Edge Function may be sufficient.
- You need each end user to connect their own Inngest account separately. Shared connectors are workspace-level, not per-end-user connections.
Common use cases and example apps
| Example app | Example prompt | Description |
|---|---|---|
| Scheduled report generator | Run a function every Monday at 9am that generates a weekly summary and emails it to the team. | Automate recurring tasks on a schedule without managing infrastructure. |
| Post-signup onboarding flow | When a user signs up, send a welcome email immediately, then a follow-up email 3 days later. | Orchestrate multi-step delayed workflows triggered by app events. |
| Data sync pipeline | Every hour, pull new records from an external API and upsert them into the database. | Run periodic background syncs that retry automatically on failure. |
| Processing pipeline | When a user submits a description, create a base image, fan out to create multiple sizes, save them and email when done. | Fan out heavy/slow/unreliable processing to improve speed and reliability. |
How Inngest connections work
Each Inngest connection uses one Inngest Event Key and one Signing Key. Within your Lovable workspace:- You can create multiple Inngest connections.
- Each connection is a separate credential setup.
- Multiple projects can use the same connection.
How to connect Inngest
Workspace admins and owners can connect Inngest. When a connection is created, Inngest becomes available across all projects in the workspace.Requirements and billing
- Available on: all plans
- Connector roles: workspace admins and owners can create and manage Inngest connections
- Additional admin controls: on Business and Enterprise plans, workspace admins and owners can enable or disable shared connector availability at the workspace level
- Prerequisites: an Inngest account with an Event Key and Signing Key
- Recommended for production: use separate Inngest environments for staging and production
Inngest usage and pricing are owned by your Inngest account. Charges for
function runs are billed by Inngest, not by Lovable.
Set up your Inngest connection
Name the connection
In Display name, enter a clear name, for example
Inngest Prod or Inngest Staging.Enter credentials
Paste your Inngest Event Key and Signing Key in the authentication fields. You can find these in the Inngest dashboard under Settings -> Keys.
FAQ
Do I need an Inngest account to use this connector?
Do I need an Inngest account to use this connector?
Yes. You need your own Inngest account and API keys to create an Inngest
connection in Lovable.
Who pays for function runs with this connector?
Who pays for function runs with this connector?
Function runs through this connector are billed by Inngest, based on your
Inngest plan and usage.
Can I create multiple Inngest connections?
Can I create multiple Inngest connections?
Yes. You can create multiple connections, for example to separate staging
and production environments.
Can end users connect their own Inngest accounts inside my app?
Can end users connect their own Inngest accounts inside my app?
Not through this shared connector flow. Shared connectors are configured at
workspace level.
What should I check first if functions are not running?
What should I check first if functions are not running?
Verify your Event Key and Signing Key, confirm the function is registered in
the Inngest dashboard, and check the Inngest function logs for errors or
failed runs.
Can I use Inngest for cron-style scheduled tasks?
Can I use Inngest for cron-style scheduled tasks?
Yes. Inngest supports cron expressions for scheduling functions on recurring
intervals, such as every hour or every weekday at a specific time.
Limitations
- An Inngest shared connector is a workspace-level credential, not a per-user connection flow.
- Functions are managed and monitored through the Inngest dashboard, not within Lovable.
- If a connected project stops triggering events after connector changes, open the connection and confirm it is still linked to the project.
How to unlink projects from a connection
Editors and above can remove specific projects from a connection without deleting the connection entirely. The connection will remain available for other projects. To unlink projects:
When unlinked, those projects will no longer have access to through this connection. If a project needs again, you can link it to any available connection.