Routines and webhooks
Run work on a schedule, watch a file for changes, or start a task from another app.
Create a routine
Step 1
Open the routines calendar
Choose Routines in the sidebar. The calendar shows your routines and scheduled calls by day or week. Use Webhooks at the top to switch to webhooks.
You're done when: you see the calendar with your routines and scheduled calls.
Step 2
Start a new routine
Choose New routine. On the calendar this button may read Create.
You're done when: the New routine dialog is open.
Step 3
Say who, what and when
- Pick the routine type:
- Bot task: one bot owns and completes each run.
- Team goal: a channel works towards a goal, and a lead coordinates it until the goal settles.
- Under Assign a bot (or the channel), choose who runs it.
- Write what should happen under What should the bot do?
- Set the start date and time, and how often it repeats: does not repeat, every day, every weekday, every hour, or every so many minutes (from 5 to 1,440).
You're done when: the bot, the task and the schedule are filled in.
Step 4
Schedule it
Choose Schedule routine.
Under More options you can choose what happens If the last run is still going (Skip this time or Queue one run), a run limit, and where it Runs on.
You're done when: your routine shows on the calendar.
Instructions can be up to 100,000 characters, and the editor tells you before you go over. Each routine keeps one conversation, named after it, and every run happens there with a divider between runs.
Let a bot propose one
Ask a bot for something on a schedule, such as "every Monday at 9, send me last week's numbers". It proposes a routine and shows a Confirm this routine card. Nothing is scheduled, changed, paused or deleted until you choose Confirm.
Manage routines
- Run now. Run now runs a routine straight away.
- Pause and resume. Pause routine keeps its history but stops new runs. Resume starts it again.
- Records. Each run leaves a record, and results also appear under Results in your Inbox.
- Problems. If runs fail, a problems marker appears. Open it for the list and a count of failures in a row.
When runs happen
- Your computer must be on and Murage running when a routine is due.
- A run up to 12 hours late still runs. Later than that, it's marked as missed.
Each routine's approval level
Each routine runs at its own approval level: Ask, Auto, Full access or No limits. Set it in the routine editor under AdvancedApprovals for this routine, or from the approval chip in the routine's own conversation.
A routine you haven't set shows Same as and the bot's name, and follows the bot's level at the moment each run starts. So a bot on No limits runs its own routines at that level too. The routine's conversation, its editor and its approval cards all show the level that actually applies. Reading your keys always asks.
An approval card raised by a routine offers Always allow for this routine. It covers that same command or place for that routine only, on every later run. Other routines and ordinary conversations with the same bot still ask. The routine editor lists these under Always allowed for this routine, each with Remove.
When a routine needs you
When a run hits a question or an approval, Murage tells you at once that the routine is waiting on you, and the run ends as Waiting on you, ready for your answer. The card stays in the routine's conversation. Open it with Review, answer, and the routine carries on from there.
Watch a file
Choose Watch a file to have Murage check a file in a bot's working folder every few minutes and tell you when it changes. Watching is read-only: no bot runs and no provider charges. Changes appear in your Inbox. Files can be up to 1 MB.
Webhooks
A webhook starts a task for a bot when another app sends a request to Murage.
Step 1
Open the Webhooks tab
Open RoutinesWebhooks.
You're done when: you see the Webhooks tab.
Step 2
Create the webhook
Choose New local webhook and pick the bot and what it should do with each event. The button may read Create local webhook.
You're done when: Murage shows you an address and a secret.
Step 3
Copy the address and secret
Copy the address and secret it gives you into the other app.
You're done when: the other app has them.
The webhook receiver listens only on your own computer, at 127.0.0.1:8800. Use a bearer token where the sending app supports headers; otherwise use the secret address. To receive events from the internet, you need your own tunnel to that receiver.
Webhook-started tasks are judged as Auto for approvals, because someone other than you wrote the input. Turns started outside the desktop (a webhook or a chat app) also skip your Always allow grants, so those actions wait for your approval.