Automation
Automate Bizisy with Zapier, Make and n8n
Zapier, Make and n8n connect Bizisy to thousands of other apps without code. A change in Bizisy starts a workflow (someone is hired, changes job or leaves; a team is created; a checklist starts), and a workflow can change Bizisy (hire someone, update a profile, change a job, start a checklist, find a person).
Everything goes through the same API and webhooks you can call yourself, with the same permissions, checks and Activity record as the web app.
Pick your tool#
Each page shows how to connect: with the Bizisy app where one is available on that platform, otherwise with Bizisy's webhooks to start the workflow and the platform's own HTTP step to call the API with your key.
What you need#
- A Manage API key (API keys). Actions run with the access of whoever owns the key: an HR key can hire, a viewer's key can only read.
- For triggers, an owner or admin: only they can send company data to another place. A Bizisy app subscribes to one event type with the owner's or admin's key when a trigger is turned on (
webhooks.subscriptions.create) and unsubscribes when it is turned off; without the app, the owner or admin adds the platform's webhook address in Bizisy.
What a trigger receives#
The same JSON as any webhook: the event type, when it happened, the ids and dates of the change and, for people, structure and positions, the record's public and job details. Never private details (personal contact, address, birthday, payroll identifiers) and never pay: workflows that need more read them with the API, as your key allows.
These events can start a workflow:
person.hiredperson.updatedperson.job_changedperson.terminatedperson.rehiredperson.erasedunit.createdunit.updatedunit.archivedlocation.createdlocation.updatedlocation.archivedlegal_entity.createdlegal_entity.updatedlegal_entity.archivedmember.role_changedmember.invitedmember.joinedfeatures.changedposition.createdposition.updatedposition.filledtitle.createdtitle.updatedtitle.mergedtitle.archivedapproval.decidedchecklist.startedchecklist.completedchecklist.task.assignedchecklist.task.status_changedannouncement.publishedannouncement.acknowledgedpay_report.finaliseddocument.addeddocument.updateddocument.signature.updateddocument.deleteddocument.generateddocument.template.publisheddocument.prepareddocument.sentdocument.clause.publisheddocument.policy.publisheddocument.policy.acknowledgeddocument.policy.retiredpayroll.period.lockedpayroll.reconciledpayroll.export.createdasset.assignedasset.returnedtimeoff.bookedtimeoff.cancelledtimeoff.decidedtimeclock.punchedtimeclock.correctedtimeclock.overtime_decidedtimeclock.month_closedshifts.week.publishedshifts.request.approvedhiring.job_openedhiring.job_closedhiring.application_receivedhiring.application_movedhiring.application_hiredhiring.interview_bookedhiring.interview_cancelledhiring.offer_senthiring.offer_acceptedhiring.offer_declinedhiring.feedback_submittedtraining.record.createdtraining.record.confirmedbenefits.benefit.createdbenefits.enrolment.changedsurveys.survey.openedsurveys.survey.closedsurveys.response.submittedsurveys.round.closedtalent.cycle.launchedtalent.cycle.closedtalent.goal.updatedtalent.profile.updatedcomp.bonus_plan.releasedcomp.cycle.released
Safety rails#
- Every owner and admin is emailed when a trigger subscribes, so nobody can quietly send data elsewhere.
- Subscriptions show in Integrations → Webhooks, marked with their app. An owner or admin can turn one off or delete it there at any time.
- A company has at most 50 automation subscriptions, besides the endpoints added in the app. When a platform answers
410 Gone(the workflow no longer listens), Bizisy removes the subscription. - When the key that subscribed is revoked, or its owner is no longer an owner or admin, Bizisy removes its subscriptions.
- AI assistants connected to Bizisy can list and remove subscriptions but never create one.
- Writes are rate limited per key (300 requests a minute) and recorded in Activity with the key's name.
Something missing or wrong on this page? Write to hello@bizisy.com.