Business apps

Flows

Automate work between Bramble apps and the outside world by connecting triggers and steps on a canvas, no code needed.

Bramble Flows automates the jobs you'd otherwise do by hand. You build a flow on a canvas: a trigger that starts it, then steps that do the work. Open it at /flows on your organisation's address.

#Triggers: what starts a flow

  • By hand, with a button.
  • On a schedule, such as every weekday at 9am.
  • A webhook: another system calls the flow's private address. See Webhooks and integrations.
  • Something happens in Bramble: a new ticket, an RMM alert, a form response, a new starter in HR, and many more.
  • Audit activity in your organisation.
  • A new email arrives in a mailbox.

#Steps: what a flow can do

  • Call any web address, send email, and post to team chat.
  • Bramble steps that work in Bramble as the person who owns the flow, such as creating a ticket or a task.
  • Run a script on a device managed by RMM, or send a request from that device to something on your own network.
  • Code steps for anything else, in a safe, sandboxed JavaScript.
  • Tables to keep data between runs, approvals and forms that wait for someone to answer, sub-flows, file transfer (FTP and SFTP), and, for MSPs, for each customer.

Every run is kept with its history. Steps can retry, and error branches handle failures. Flows keep versions as you edit, and you can import workflows built in other automation tools.

Note

Flows can't reach private or internal networks directly. To reach something on your own network, use a step that runs from one of your RMM devices.

#Licence and settings

Licence Flows, per person
Organisation-wide flows and everyone's flows Flows Admin role (building your own flows needs no role)

For developers

Articles for this app are on their way.