Autotask
Workflows create and update tickets, set queues and priorities, and pull client context into other steps. Intake forms become tickets automatically, and completed runs write their results back so the PSA stays the system of record.
Workflow automation integrations
Connect the stack you already run.
Workflows are only useful if they reach the systems where the work actually lives. W!FE ships with built-in integrations for the platforms below, and Braintek connects anything else through a custom REST API connector. Read about the platform itself on the product page.
Autotask
Microsoft Graph
Microsoft 365
Teams
Exchange Online
NinjaOne
IT Glue
ImmyBot
Pax8
SMTP2GO
SQL
PowerShell
OpenAI
Custom API +
Built-in integrations
What workflows actually do with each one.
These connectors exist because real workflows needed them. Braintek, the MSP that built W!FE, runs its own operations on them every day, and the MSP page shows what those workflows look like in practice.
NinjaOne
Alerts from NinjaOne trigger workflows through webhooks. Workflows deduplicate noise, run safe remediation, and only open a ticket when a person is needed. Device data also feeds reporting and onboarding checks.
IT Glue
Workflows write documentation as a side effect of doing the work. When onboarding provisions an account or deploys software, the record lands in IT Glue in the same run, so documentation stays current without anyone updating it by hand.
ImmyBot
Onboarding workflows hand off to ImmyBot to deploy the software baseline for a new user or device. The workflow tracks the deployment as a step, so setup is verified rather than assumed.
Pax8
Workflows assign and reclaim licenses through Pax8 as part of onboarding and offboarding. License changes happen in the same run as the account changes, which keeps billing aligned with reality.
Microsoft 365 and Graph
Microsoft Graph gives workflows deep reach into Microsoft 365: creating users, setting group membership, managing mailboxes and calendars, and reading or writing files. Most onboarding and offboarding automation runs through this connector.
Teams
Workflows post updates and approval requests into Teams channels and chats. An approval gate pauses the run, pings the approver where they already work, and resumes when they respond.
Exchange Online
Offboarding workflows convert mailboxes, set forwarding, and manage permissions in Exchange Online. Mailbox rules and delegation changes run as auditable steps instead of manual admin work.
SMTP2GO
Workflows send transactional email through SMTP2GO: confirmations when a form is received, reports on a schedule, and notifications to people outside your Microsoft tenant.
SQL databases
Workflows read from and write to SQL databases directly. That means syncing records between systems, building recurring reports from live data, and using your own database as a source of truth inside a workflow.
PowerShell
When a task needs real scripting, workflows run approved PowerShell as a step. Scripts run from a controlled library, sensitive ones sit behind approval gates, and every execution lands in the run history.
OpenAI
Workflows use OpenAI steps to classify inbound requests, summarize long text, and draft responses that a person reviews. AI does the reading and sorting, then the workflow routes the result.
Custom API connector
If it has a REST API,
W!FE can reach it.
The built-in list is a starting point, not a boundary. Braintek connects any system with a REST API or an OpenAPI definition through the custom connector. Tools like Clio, QuickBooks, or ServiceTitan are reachable this way, along with the industry software your business already depends on.
Ask about your stack01
Tell us the tool. If it has API documentation, Braintek can evaluate the connection before you commit to anything.
02
Braintek builds the connection. The custom connector wraps the API so your workflows use it like any built-in step.
03
It stays maintained. When the vendor changes their API, Braintek updates the connection. That is part of the operated service, not a change order.
Common questions
Integrations, answered.
What if my tool is not listed?
If your tool has a REST API or an OpenAPI definition, Braintek can connect it through the custom API connector. That covers most modern business software, including practice management, accounting, and field service platforms.
Do integrations cost extra?
No. Every plan includes the built-in integrations and the custom API connector. Pricing is based on workflows and runs, not on which systems you connect.
Who builds and maintains the connections?
Braintek does. We build your dedicated environment, set up each connection, and keep everything working as vendors change their APIs. You see every workflow and every run, but you never maintain the plumbing.
How is authentication handled?
Credentials are stored in Azure Key Vault, and connections are maintained by Braintek. Workflows reference secured connections rather than raw passwords or keys.
Start with one process
Your stack is probably already covered.
Tell us the systems your process touches. We will map the first workflow free.