Workflow automation that does the busywork for your projects

In Brainitive, rules assign, move and update issues for you when something happens. GitHub activity shows up on the issue it mentions, and signed webhooks send events to your own systems. A grouped inbox and push notifications tell you what needs your attention.

Workflow automation

An automation rule says: when something happens, if the issue or ticket matches your conditions, then do these actions. Project admins build rules in a visual editor that shows each rule in plain words.

  • Six triggers: issue created, issue moved (optionally to a specific column), issue assigned, comment added, due date passed and helpdesk ticket created.
  • Up to 10 conditions per rule on board, column, type, priority, labels, assignee, reporter, title, description, dates and your custom fields, matched with All or Any.
  • Up to 10 actions run in order: assign, move to column, set priority, set type, set due date, add label, add a comment, notify, or create a linked issue from a ticket.
  • Test on an issue runs a rule as a dry run and shows which conditions pass and what each action would do. New rules start switched off.
  • A run history logs every run with its conditions and action results and keeps runs for 30 days. Changes made by a rule never trigger other rules, so there are no loops.

GitHub development

Connect GitHub in one click with the Brainitive GitHub App, and branches, commits, pull requests and deployments appear in the Development section of the issue they mention.

  • Issues are linked by their issue key in a commit message, a branch name or a pull request title, for example fix(BRAI-123) or feat/brai-123-login.
  • Merge transitions move a card to the column you choose for each board when its primary pull request is merged. A card is never moved out of a done column.
  • The app only reads. It asks for read access to metadata, contents, issues, pull requests and deployments.
  • On Brainitive Cloud the GitHub App is already set up. Self-hosted admins create their own app in one click under Instance admin, GitHub App.
  • Sign in with GitHub is a separate option, so you can use either one without the other.

Outgoing webhooks

Outgoing webhooks send an HTTPS POST to your URL whenever something happens in a workspace. Use them with Zapier, Make, n8n or your own service.

  • 17 events across issues, pages, sprints, helpdesk tickets, leads, time entries and billing reports, for example item.created, item.moved, sprint.completed, ticket.created and billing_report.paid.
  • Every request is signed with an X-Brainitive-Signature header: sha256= plus an HMAC-SHA256 of the timestamp, a dot and the raw body, using your signing secret.
  • 5xx, 429 and network errors are retried after 30 seconds, 2 minutes and 10 minutes. After 10 failures in a row the webhook is turned off and workspace admins are notified.
  • Send test sends a ping, and the delivery log shows every attempt and the answer your server gave.
  • Admins can reveal or rotate the signing secret at any time. The URL must use https and point to a public address.

Notifications & push

Brainitive collects mentions, assignments, comments, due dates and more in a grouped inbox. You choose for each category whether a notification shows in the app, as a push notification or by email.

  • The bell and the inbox have All, Unread, Mentions and Assigned tabs, grouped by Today, Yesterday, This week and Older, with archive, bulk actions and keyboard shortcuts.
  • 13 categories, including mentions, assignments, comments, status changes, reminders and due dates, sprints, helpdesk, leads, reviews and approvals, and bookings.
  • Web push reaches your desktop or phone even when Brainitive isn't open, on Windows, macOS, Linux and Android, and on iPhone and iPad from the Home Screen app (iOS 16.4 or later).
  • Your devices lists every registered browser, with Send test, expired subscriptions and tips for Focus or Do not disturb.
  • A morning task summary at 8:00 lists your tasks that are due today or overdue.

Frequently asked questions

Which events can trigger an automation in Brainitive?

A rule can start when an issue is created, moved to another column, assigned, commented on, or passes its due date, or when a helpdesk ticket is created. The issue moved trigger can be limited to a specific target column. The due date trigger is checked every few minutes and runs once per issue and due date.

What can a Brainitive automation do?

A rule can assign a member, move an issue to a column, set the priority, type or due date, add a label, post a comment or notify someone. For helpdesk tickets it can create a linked issue on a board. A rule can run up to 10 actions in order, and each run is logged in the run history.

Does Brainitive integrate with GitHub?

Yes. The Brainitive GitHub App links branches, commits, pull requests and deployments to issues by their issue key, for example BRAI-123 in a branch name or commit message. You can also have a merged pull request move the card to a column you choose. The app only needs read access to your repositories.

How do I verify a Brainitive webhook signature?

Each request carries an X-Brainitive-Timestamp and an X-Brainitive-Signature header. Compute an HMAC-SHA256 over the timestamp, a dot and the raw request body with your signing secret, and compare it with the signature after sha256= using a constant-time comparison.

Can I connect Brainitive to Zapier, Make or n8n?

Yes. Add an outgoing webhook under Workspace settings, Webhooks, paste the URL from Zapier, Make or n8n, and choose all events or only the ones you need. Brainitive sends events for issues, pages, sprints, tickets, leads, time entries and billing reports as signed JSON.

Does Brainitive send push notifications to my phone?

Yes. Turn on push under Profile settings, Notifications, and register each browser or device you use. Push works on desktop and Android browsers, and on iPhone and iPad from the Home Screen app on iOS 16.4 or later. You choose per category whether you get in-app, push or email notifications.

More in the docs: Automations · GitHub · Outgoing webhooks