Spojit
Triggers

Every way to start
a workflow

Start a workflow however the work shows up. Webhooks for software, a per-workflow email address for messages, schedules for time-based work, manual runs on demand, and calls from other workflows. One workflow can have many ways in.

Webhooksigned HTTP
Mailhookinbound email
Schedulecron / interval
Manualrun on demand
Chainedfrom another workflow
start
Order sync
Any trigger starts the same run
ready
How it works

However the work arrives

01

Pick a trigger

Choose how the workflow should start, from a webhook to a schedule to an inbound email.

02

Configure it

Set up the endpoint, address, or schedule. Spojit handles the plumbing behind each one.

03

The workflow runs

However the trigger fires, the same workflow runs with the incoming data as its input.

Capabilities

A trigger for every source

Webhooks

A signed HTTP endpoint for any software that can make a request. Verified, with an execution id back.

Mailhook

A per-workflow email address. Send or forward a message and the workflow runs in seconds.

Schedules

Cron expressions or simple intervals, in your timezone, with no server to keep running.

Manual runs

Kick off a workflow on demand from the app, with the inputs you provide at run time.

Chained calls

Let one workflow start another as a step, so you compose larger processes from smaller ones.

Mix and match

A single workflow can accept more than one trigger, so the same logic serves several sources.

Use cases

Start it from anywhere

App events

Turn an order, a payment, or a merged change in another tool into a run via a webhook.

Inbound email

Forward a message to a mailhook and let an email start the workflow, no integration required.

Recurring work

Run nightly syncs, reports, and reconciliations on a schedule that fires on its own.

On demand

Let a person run a workflow themselves whenever they need it, with the inputs they choose.

The difference

Event vs schedule

Start on an event when something happens, and on a schedule when the clock is the trigger.

Trigger on an event when

  • An app or a person initiates the work
  • Timing is driven by something outside Spojit
  • You want a run the instant it happens

Trigger on a schedule when

  • The work happens at set times
  • Nothing external will tell you to start
  • Runs should recur predictably

Start your workflow your way

Start free and wire up your first trigger, whichever way your work arrives. No card needed.