NebulaNebula

Jobs

Jobs run your agents automatically — on a schedule, from an app event, or via webhook. Turn anything you ask Nebula to do once into a recurring job.

A job runs an agent automatically — on a schedule, when something happens in a connected app, or from an incoming webhook. Find your jobs in the Jobs tab in the sidebar, or just tell Nebula when to repeat any task. The mechanism behind every job is a trigger; there is no separate automation system to learn.

Three trigger types

Schedule

Every weekday at 9am, every Monday, the first of the month. Say the cadence; Nebula handles the cron.

Event

Fire when something happens in a connected app — a Slack message, a Twitter mention, a Discord post.

Webhook

Accept payloads from Zapier, Make, Stripe, or anything that can POST.

Creating a trigger

After any task, just say when to repeat it. Nebula creates the trigger and runs it from then on.

Y
You

Run this every weekday at 9 AM.

Create trigger

Creating scheduled trigger: every weekday at 9:00 AM.

Nebula

Scheduled — this task will run every weekday at 9 AM your local time.

It works the same for events and webhooks:

Y
You

When someone mentions me on Twitter, notify me in Slack.

Create trigger

Creating event trigger: on new Twitter mention.

Nebula

Trigger active. Whenever you're mentioned on Twitter, I'll DM you in Slack.

Scheduled triggers

Say it in plain English — "every weekday at 9 AM", "every Monday morning", "once a day at 5 PM Eastern" — Nebula picks the right cron and the right timezone. Schedules can run as frequently as once every 15 minutes.

For specific intervals, use one of the presets or write a custom cron:

PresetCron
Every 15 minutes*/15 * * * *
Every hour0 * * * *
Daily at 9:00 AM0 9 * * *
Weekdays at 9:00 AM0 9 * * 1-5
Weekly on Monday0 9 * * 1
Monthly on the 1st0 9 1 * *

Open the trigger details panel and pick Custom cron… to enter any valid expression. Useful for non-standard intervals like "every 3 hours" or "twice daily at 8 AM and 6 PM".

Event triggers

Connect Slack, Discord, Telegram, or Twitter to your workspace and Nebula can react to events from those platforms in real time.

New message, reaction added or removed, file shared, channel created / archived / renamed, member joined or left, pin added or removed, emoji changed.

Reaction added or removed, member joined or left, channel created or deleted.

New message, photo / video / audio / voice, document, member joined or left.

New tweet, tweet liked, follow or unfollow, block or mute, direct message.

Webhook triggers

Webhook triggers give you a unique URL any external service can POST to. Useful when Nebula doesn't have a native integration but the service can send outbound webhooks — Zapier, Make, Stripe, CI/CD pipelines, monitoring tools.

Open Jobs in the sidebar and click New triggerWebhook.
Give it a name and describe what Nebula should do when the webhook arrives. Set the delivery destination.
Nebula generates a unique URL — https://nebula.gg/webhooks/<token>. Paste it into the source service.
Any HTTP POST to that URL fires the trigger; the request body is passed to the task as context.

Webhook URLs are secrets — anyone with the URL can fire the trigger. Treat them like an API key. Rotate from the trigger panel if needed.

Need help setting up a trigger? Ask Nebula directly in chat first — it can create, pause, and edit triggers for you. For bugs or anything unresolved, email support@nebula.gg. See Support for more options.

Where triggers live

Every trigger has two parts:

A trigger condition — the schedule, event, or webhook that starts it.
A task recipe — the prompt and execution steps Nebula follows, including which agents handle each step and where to deliver the result.

Open any trigger from the Jobs page in the sidebar, or from an agent's details panel, to see and edit the description, condition, delivery channel, prompt, execution steps, and activity log.

Managing through chat

Most workspaces never visit the Jobs page — they just ask Nebula directly.

Y
You

Show me my triggers.

Nebula

You have 3 active triggers:

  1. Standup Summary — weekdays at 10 AM
  2. Morning News Digest — weekdays at 9 AM
  3. Twitter Mentions — on every mention
Y
You

Pause the morning news digest.

Run action

Pausing the Morning News Digest trigger.

Nebula

Paused. You can resume it anytime.

Y
You

Change the morning briefing to run at 8 AM instead of 9 AM.

Run action

Updating trigger schedule to 8:00 AM.

Nebula

Updated — the morning briefing will now run at 8 AM.

Pausing vs deleting

PauseDelete
Stops firingYesYes
Can be resumedYesNo
Keeps run historyYesNo
Best whenTemporarily quiet (vacation, freeze)Done with it for good

On this page