Apps › Developer Tools

GitHub automation with Bizomate

The people who need to know about a release or a failed build are rarely watching GitHub. Bizomate starts a workflow the moment something happens in a repository and tells them where they already are. It also opens issues, commits files, publishes releases and runs GitHub Actions workflows when another app says so. Every run leaves a record you can read.

Start free

On every plan, Free included.

At a glance

Label	Value
Plans	Every plan
Connect	Paste a token
Starts runs	Instantly
Kind	Connected app · Developer Tools

What can start a workflow

New issue
When an issue is opened

Only when an issue is opened; editing, labelling or closing one does not start a run.

New pull request
When a pull request is opened

Pull request merged
When a pull request is merged

Only when a pull request is closed by merging. Merging is also a push to the branch it went into, so a workflow on Push to a branch runs too.

Push to a branch
When commits are pushed

Fill in Only this branch to hear one branch; left empty, tag pushes and deleted branches start runs as well.

New release
When a release is published

When a release is published, pre-releases included. Saving a draft does not; publishing it later does.

New star
When someone stars the repository

Workflow run finished
When a GitHub Actions run finishes

Hears every Actions workflow in the repository. Under When it, choose Finishes, Succeeds or Fails.

What a workflow can do with it

Create an issue
Opens an issue in a repository

Update an issue
Changes an issue's state, title, labels or assignees

Add a comment
Comments on an issue or pull request

Find issues
Issues by state, labels and date — one item each

By state, labels and the date they changed, one item each.

Create a pull request
Asks to merge one branch into another

Merge a pull request
Merges a pull request

As a merge commit, a squash or a rebase.

Get a pull request
A pull request's state, branches and whether it can merge

Create or update a file
Commits a file to a branch

Commits text you write, or a file from an earlier step, to a branch.

Get a file
A file's text, and the file itself for later steps

Its text, and the file itself for later steps.

Create a release
A release for a tag, with notes

Upload a release asset
Attaches a file from an earlier step to a release

A file from an earlier step, attached to the release with that tag.

Run a workflow
Starts a GitHub Actions workflow that has workflow_dispatch

A GitHub Actions workflow that has workflow_dispatch, on the branch you choose, with its inputs.

How you connect it

Make a personal access token in GitHub — under Settings › Developer settings › Personal access tokens — fine-grained and limited to the repositories you choose, or classic. Give it the permissions the steps you use need; the connect article lists them step by step. Paste it into Bizomate under Personal access token. Everything the steps do is done as the person who made the token. Bizomate asks GitHub who the token belongs to before saving it, and Test answers "Reached @{your username} · {n} repositories".

GitHub triggers add a webhook to the repository when you publish, so there is nothing to paste — but adding one needs the token's owner to be an admin of the repository, and a fine-grained token needs Webhooks: Read and write. Signing in with GitHub instead of a token is not offered yet.

The token is encrypted before it is saved, used only when a step runs, a trigger is set up or a test calls GitHub, and never shown again — not to you, your colleagues or Bizomate support. It belongs to one workspace, the Code step cannot read it, and revoking the connection wipes it at once.

In the help centre: Connect GitHub, Start a workflow from GitHub events, Create, update or find GitHub issues, Create, merge or get a GitHub pull request, Create, update or get a file in GitHub, Create a GitHub release or upload an asset, Run a GitHub Actions workflow and How instant triggers work.

Questions about GitHub

Do I need to set up a webhook in GitHub?

No. Publishing a workflow with a GitHub trigger adds the webhook to the repository, with a secret of its own that GitHub signs every event with. Each published workflow has its own webhook, and changing the trigger or deleting the workflow takes it away.

Why does publishing say GitHub would not add a webhook?

Adding a webhook needs the token's owner to be an admin of the repository; write access is not enough. A fine-grained token also needs Webhooks: Read and write. Fix either, then publish again.

Can I tell the team only when a build fails?

Yes. Use Workflow run finished and choose Fails under When it. To act on one Actions workflow only, add an IF step on the workflow's name.

What happens when the token expires?

Every GitHub step then fails with "Bad credentials". Give the expiry date when you connect, and the workspace's admins are reminded 30, 7 and 1 days before; Replace token swaps in a new one without any workflow failing in between.

Can a form or another app open an issue?

Yes. Create an issue takes a title, body, labels and assignees from earlier steps — a form, an email, a support ticket — and gives back the issue's number and link for the next step.

Guides that use GitHub

When something fails

How to tell your team in Teams when a GitHub Actions run fails

Every failed GitHub Actions run, posted in your team's Teams channel.

4 min read

Reports

How to share GitHub release notes in Slack and by email

Every GitHub release's notes, in your Slack channel and by email.

4 min read