Operations
Workflows that run themselves, on the cadence the work demands.
TexAu workflows run on cron, on calendar, on inbound signal, or on demand. Schedule the daily LinkedIn pull, the weekly enrichment refresh, the hourly intent sweep — and let the bench tend itself.
What you get
The capabilities, concrete.
Cron + calendar
Plain English ("every weekday at 9am UTC") or full cron syntax. Both first-class.
Time-zone aware
Schedules run in the time zone you specify per workflow. DST handled correctly.
Signal-triggered runs
Trigger on inbound webhook, CRM stage change, form submit, or Slack command.
Concurrency control
Cap parallel runs per workflow so you never overload an upstream provider.
Run history
Every run logged with duration, rows processed, credits, errors. Searchable.
Pause + resume
Pause from the UI or API. Pick up exactly where you left off.
How it works
The shape of the workflow.
Open any workflow. Add a Schedule. Pick a frequency — cron, calendar, or signal. TexAu queues the runs, executes with the concurrency cap you set, and posts results to the destinations the workflow already knows about.
FAQ
Frequently asked.
- Can I schedule workflows on cron?
- Yes — cron expressions, plain-English calendar rules, or signal triggers. Time-zone aware.
- How are concurrent runs handled?
- Each workflow has a concurrency cap. New runs queue, skip, or run in parallel — your choice per workflow.
- Can I pause a scheduled workflow?
- Yes. Pause from the UI or API. Resuming continues from the next scheduled tick.
Run it on your motion
See schedulers in your own workspace.
Free to start. No demo required. Five minutes to first run.