Sound familiar?
What teams on Power Automate tell us before a project starts.
- Approvals run through email chains and nobody knows who is holding things up.
- Documents arrive in Outlook and someone saves them to SharePoint by hand.
- A flow broke when the person who made it left.
- We hit a premium connector or licensing question and don't know the options.
- We need data from a system outside Microsoft and the connector doesn't exist.
What we build
Each one is a working piece you can open and check when it's done.
Approval flows
Requests for purchases, time off or documents sent to the right approver in Teams or Outlook, with reminders, escalation and a record of the answer.
n8n, Make and Zapier automationDocument filing
Attachments and forms saved to the correct SharePoint library or folder, named the same way every time, with the details written to a list.
n8n, Make and Zapier automation API integrations and data syncExcel and list updates
Rows in Excel Online or SharePoint lists created, updated and checked by flow, so reports are current without copy and paste.
n8n, Make and Zapier automationConnections outside Microsoft
Systems without a ready connector reached through their API with HTTP actions or a custom connector.
API integrations and data syncOwnership and error handling
Flows moved to shared owners or a service account where appropriate, with failure notices to a named person.
n8n, Make and Zapier automationMoving from old macros
Excel macros and email rules that someone built years ago turned into flows that can be read and maintained.
Excel and VBA toolsWhat we connect it to: SharePoint, Outlook, Microsoft Teams, Excel, Zapier, Make, Power BI.
Industries that use it: Engineering firms, Nonprofits, Schools and tutoring, IT / MSP.
Example projects
Illustrations of the shape of the work, not past clients. Yours gets its own written scope.
Example project
Purchase request approval
Example: an office wants requests entered in a form, sent to a manager in Teams for approval, then logged in a SharePoint list and emailed to purchasing.
Power Automate, Microsoft Forms, Teams, SharePointExample project
Invoices from the inbox to a folder
Example: a finance team wants supplier invoice attachments saved to a SharePoint folder by month, with the sender and date logged in an Excel table.
Power Automate, Outlook, SharePoint, ExcelExample project
Flow that calls an outside system
Example: a company wants new rows in a list to create a customer in a system that has a REST API and no Microsoft connector.
Power Automate HTTP action, SharePointQuestions people ask first
Do we need extra licences?
Some connectors and features need a premium plan and some don't. We check what your flows need against your plan and tell you before building.
Can you repair flows someone else built?
Yes. We read them first, tell you what they do and where they fail, and agree the changes before we touch them.
Who owns what you build?
You do. It is built in your own Microsoft 365 tenant, and you get short notes on how it works.
How do we start?
Tell us the process that passes through the most inboxes. We reply with questions or a written scope.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com