---
title: "Connect your app to Inngest"
description: "<p><a href=\"https://www.inngest.com/\">Inngest</a> is a workflow and background job platform that lets you run durable functions, scheduled tasks, and event-driven workflows."
---

> Documentation Index
> Fetch the complete documentation index at: https://rshift.helpcent.re/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your app to Inngest

<p><a href="https://www.inngest.com/">Inngest</a> is a workflow and background job platform that lets you run durable functions, scheduled tasks, and event-driven workflows. The Inngest app + chat connector lets your RShift Sites apps call Inngest from your workspace using a managed workspace-level connection.</p>
<p>Inngest is available as an <a href="/sites/integrations/app-connectors/">app + chat connector</a>: one shared connection that works in the project chat while you build and in your published apps.</p>
<p>Each Inngest connection uses your own Inngest credentials. After it is connected, projects in your workspace can use the connection to trigger and manage background workflows through your Inngest account.</p>
<p>Use the Inngest connector when your app needs to run work outside of a user request, such as sending delayed notifications, processing data on a schedule, or orchestrating multi-step workflows with automatic retries.</p>
<p>Use another path when:</p>
<ul>
<li>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.</li>
<li>You need each end user to connect their own Inngest account separately. App + chat connectors are workspace-level, not per-end-user connections.</li>
</ul>
<h2>Common use cases and example apps</h2>
<table>
<thead>
<tr>
<th style="text-align: left">Example app</th>
<th style="text-align: left">Example prompt</th>
<th style="text-align: left">Description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align: left">Scheduled report generator</td>
<td style="text-align: left"><em>Run a function every Monday at 9am that generates a weekly summary and emails it to the team.</em></td>
<td style="text-align: left">Automate recurring tasks on a schedule without managing infrastructure.</td>
</tr>
<tr>
<td style="text-align: left">Post-signup onboarding flow</td>
<td style="text-align: left"><em>When a user signs up, send a welcome email immediately, then a follow-up email 3 days later.</em></td>
<td style="text-align: left">Orchestrate multi-step delayed workflows triggered by app events.</td>
</tr>
<tr>
<td style="text-align: left">Data sync pipeline</td>
<td style="text-align: left"><em>Every hour, pull new records from an external API and upsert them into the database.</em></td>
<td style="text-align: left">Run periodic background syncs that retry automatically on failure.</td>
</tr>
<tr>
<td style="text-align: left">Processing pipeline</td>
<td style="text-align: left"><em>When a user submits a description, create a base image, fan out to create multiple sizes, save them and email when done.</em></td>
<td style="text-align: left">Fan out heavy/slow/unreliable processing to improve speed and reliability.</td>
</tr>
</tbody>
</table>
<h2>How Inngest connections work</h2>
<p>Each Inngest connection uses one Inngest Event Key and one Signing Key.</p>
<p>Within your RShift Sites workspace:</p>
<ul>
<li>You can create multiple Inngest connections.</li>
<li>Each connection is a separate credential setup.</li>
<li>Multiple projects can use the same connection.</li>
</ul>
<p>This helps you separate environments, such as staging and production.</p>
<h2>How to connect Inngest</h2>
<p>Workspace <strong>admins</strong> and <strong>owners</strong> can connect Inngest.</p>
<p>When a connection is created, Inngest becomes available across all projects in the workspace.</p>
<h3>Prerequisites</h3>
<ul>
<li><strong>Connector roles:</strong> workspace admins and owners can create and manage Inngest connections</li>
<li><strong>Additional admin controls:</strong> on Business and Enterprise plans, workspace admins and owners choose who can create connections per connector, as described in <a href="/sites/integrations/admin-controls/#who-can-create-connections-and-clients">Who can create connections and clients</a></li>
<li><strong>Prerequisites:</strong> an Inngest account with an Event Key and Signing Key</li>
<li><strong>Recommended for production:</strong> use separate Inngest environments for staging and production</li>
</ul>
<blockquote>
<p><strong>Note</strong></p>
<p>Inngest usage and pricing are owned by your Inngest account. Charges for
function runs are billed by Inngest, not by RShift Sites.</p>
</blockquote>
<blockquote>
<p><strong>Danger</strong></p>
<p>App + chat connector connections are workspace-level. Anyone in the workspace who
can use connected projects can use the Inngest connection in those projects.</p>
</blockquote>
<h3>Set up your Inngest connection</h3>
<p><strong>Open the connector</strong></p>
<p>Open <strong>Connectors</strong> and select <strong>Inngest</strong>.</p>
<p><strong>Add a connection</strong></p>
<p>Click <strong>Add connection</strong>.</p>
<p><strong>Name the connection</strong></p>
<p>In <strong>Display name</strong>, enter a clear name, for example <code>Inngest Prod</code> or <code>Inngest Staging</code>.</p>
<p><strong>Enter credentials</strong></p>
<p>Paste your Inngest Event Key and Signing Key in the authentication fields. You can find these in the Inngest dashboard under <strong>Settings -&gt; Keys</strong>.</p>
<p><strong>Create the connection</strong></p>
<p>Click <strong>Create</strong>.</p>
<p><strong>Use it in your app</strong></p>
<p>Prompt RShift Sites to add background jobs or scheduled workflows that use Inngest, then test by triggering an event and checking the Inngest dashboard for function runs.</p>
<h2>FAQ</h2>
<p><strong>Do I need an Inngest account to use this connector?</strong></p>
<p>Yes. You need your own Inngest account and API keys to create an Inngest
connection in RShift Sites.</p>
<p><strong>Who pays for function runs with this connector?</strong></p>
<p>Function runs through this connector are billed by Inngest, based on your
Inngest plan and usage.</p>
<p><strong>Can I create multiple Inngest connections?</strong></p>
<p>Yes. You can create multiple connections, for example to separate staging
and production environments.</p>
<p><strong>Can end users connect their own Inngest accounts inside my app?</strong></p>
<p>Not through this app + chat connector flow. App + chat connectors are configured at
workspace level.</p>
<p><strong>What should I check first if functions are not running?</strong></p>
<p>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.</p>
<p><strong>Can I use Inngest for cron-style scheduled tasks?</strong></p>
<p>Yes. Inngest supports cron expressions for scheduling functions on recurring
intervals, such as every hour or every weekday at a specific time.</p>
<h2>Limitations</h2>
<ul>
<li>An Inngest app + chat connector is a workspace-level credential, not a per-user connection flow.</li>
<li>Functions are managed and monitored through the Inngest dashboard, not within RShift Sites.</li>
<li>If a connected project stops triggering events after connector changes, open the connection and confirm it is still linked to the project.</li>
</ul>
<h2>Manage your {connector_0} connection</h2>
<p>Connections are managed from <a href="https://lovable.dev/dashboard?connectors"><strong>Connectors</strong></a>: select <strong>{connector_0}</strong>, then open the connection.</p>
<ul>
<li><strong>Unlink projects</strong> to remove {connector_0} access from specific projects while keeping the connection available for others. See <a href="/sites/integrations/app-connectors/#unlink-projects-from-a-connection">Unlink projects from a connection</a> for the steps.</li>
<li><strong>Delete the connection</strong> to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use {connector_0} stop working until a new connection is added. See <a href="/sites/integrations/app-connectors/#delete-a-connection">Delete a connection</a> for the steps and who can delete.</li>
</ul>
<h2>Related topics</h2>
<ul>
<li><a href="/sites/integrations/workday/">Connect your app to Workday</a></li>
<li><a href="/sites/integrations/notion/">Connect your app to Notion</a></li>
<li><a href="/sites/integrations/granola/">Connect your app to Granola</a></li>
<li><a href="/sites/integrations/slack/">Connect your app to Slack</a></li>
<li><a href="/sites/integrations/ashby/">Connect your app to Ashby</a></li>
</ul>

Source: https://rshift.helpcent.re/sites/integrations/inngest/index.mdx
