Skip to content
SharePoint automation · Australia

SharePoint automation services in Australia

Approvals and filing that run by themselves, inside your own SharePoint.

SharePoint holds the documents and lists of many Australian businesses, and a lot of the work around it is still done by hand. If you want to automate SharePoint, these are the usual jobs: asking for approvals, filing documents, updating lists and chasing people. True North Innovations is a Melbourne-based team that works with businesses across Australia. We build and repair automations on your own SharePoint, mostly with Power Automate, and we write down how each one works. All of it happens inside your own Microsoft 365 account. For apps built on the same base, see the Power Platform page.

Review · Build or repair · Clear rules · Written hand-over

Melbourne based.
Australia-wide delivery.

Melbourne · Sydney · Brisbane · Perth · Adelaide · Canberra

The problem

Where SharePoint work is still done by hand

01

Approvals by email

Someone emails a document around and then asks who has looked at it.

02

Files in the wrong place

Documents are saved with different names in different folders, and finding one takes time.

03

Lists that are out of date

A list of jobs, assets or requests is only right the day somebody updated it.

Deliverables

What we build and hand over

01

Approval flows

We build the flow so that a request goes to the right person, with a reminder and a record of who decided and when.

02

Filing rules

We build rules so that new documents are named and filed in the right library, using the details on the document or its list entry.

03

List updates

We build the flow so that when a document or an entry changes, the related list is updated and stays right.

04

Repair of flows that stopped

We find why a flow fails, fix the cause where we can and test again.

05

A written map

Each flow, what starts it, what it changes and who owns it.

06

Error alerts and training

A named person is told when a flow fails, and your team learns to read the run history.

Examples to assess. The scope is agreed in writing before work starts.

Right choice

When SharePoint automation fits and when something else fits better

The documents and lists already live in SharePoint
How we see itA natural fit. The flows can work on the data where it is.
The job reaches many outside systems
How we see itA general tool may suit better. See workflow and business process automation.
You want a small app on top of your lists
How we see itSee the Power Platform page.
You want to read and sort incoming documents
How we see itSee document automation.
You are not sure SharePoint is the right home for the work
How we see itSay so. We would rather tell you at the start, and AI consulting can help you decide.

Some features need a paid plan from Microsoft. We check what your plan includes before we build and write the answer down.

Old workflows

SharePoint workflows today, and the old ones that no longer run

A SharePoint workflow is a set of steps that runs by itself when something happens to a document or a list entry, such as a request for approval. Today these flows are built in Power Automate.

Many businesses built their approvals years ago with the older workflow tools in SharePoint. Microsoft's own page on SharePoint workflow retirement says that SharePoint 2010 workflows were retired on 1 November 2020, and that SharePoint 2013 workflows were removed from existing Microsoft 365 accounts on 2 April 2026, with no way to extend. It recommends a move to Power Automate. Both days have passed.

If an approval you rely on stopped working and nobody knows why, this may be the reason. We list what each old workflow did, rebuild each one in Power Automate inside your own Microsoft 365 account, test it on real examples and write it down. We read Microsoft's page again before we advise, because it can change.

How it works

A worked example: a new document is checked, approved and filed

A made-up example. A new supplier document is added to a library, sent for approval and filed, and a list is updated.

Demonstration with dummy data

  1. 01 · Trigger

    A document is added

    A new file lands in an intake library.

  2. 02 · AI step

    The details are read and checked

    The file name, the supplier and the type are checked against rules, and missing details are marked.

  3. 03 · Check by a person

    A person approves

    We build the flow so that it asks the named approver, with a reminder. Nothing is filed as approved until they decide.

  4. 04 · Action

    The file is moved and named

    We build a rule that renames the approved document and moves it to the right library.

  5. 05 · Record

    The list is updated

    The decision, the approver and the time are saved on the related list entry.

One document in SharePoint in five steps: the same five marks as every workflow on this website.
Errors and limits

Failed flows, missing approvers and plan limits

A flow fails
What we set upAn alert goes to a named person, with the item and the step named.
An approver is away
What we set upWe build a rule that sends the request to a named backup after a set time, so work is not stuck.
A document has missing details
What we set upIt is set aside for a person with the reason written next to it, and it is not filed as if it were complete.
Plan features and limits
What we set upThese depend on your Microsoft plan. Check Microsoft's own pages for current limits and fees, paid by you to Microsoft.
What we need from you

What you give us to start

  • Access to your Microsoft 365 with the right to build flows on the sites involved, set up so you can remove it later.
  • A list of the libraries and lists the work uses, and who owns each.
  • The approval steps today, and who decides at each step.
  • Five real documents or requests, including an awkward one.
  • A named person who owns the flows after hand-over.
How we work

A clear process: review, design, build, hand over

  1. 01

    Review

    We look at the libraries, lists and any flows that exist, and list what works and what does not.

    Output: A written map and a repair list

  2. 02

    Design

    We agree the approval steps, the filing rules and the alerts.

    Output: A short written plan

  3. 03

    Build

    We build and repair in your own account and test with real documents.

    Output: Working, tested flows

  4. 04

    Hand over

    We train your team and agree who owns each flow.

    Output: Training and written responsibilities

Cost

What affects the cost of SharePoint automation

How many libraries, lists and flows
Why it mattersEach one needs reading, rules and testing.
How many approval steps
Why it mattersMore people and more conditions mean more design.
How tidy the existing files are
Why it mattersInconsistent names and folders need clearing up before rules can be trusted.
Whether outside systems are involved
Why it mattersEach outside connection needs access, testing and a plan for change.
Microsoft's own fees
Why it mattersYour plan and its features are paid by you to Microsoft. They are separate from our work.

Every project is scoped individually.

Common questions

SharePoint automation: good to know

Can you work in the SharePoint we already have?

Yes. We work inside your own Microsoft 365, with access you give us and can remove at any time.

Do you use Power Automate?

Mostly, yes. A SharePoint automation workflow is usually built in Power Automate. Which features you can use depends on your Microsoft plan, and we check that first. See also the Power Automate page.

Our old SharePoint workflow stopped. Can you rebuild it?

Often, yes. We list what the old SharePoint workflow did, rebuild it in Power Automate inside your own Microsoft 365 account, test it and write it down. See the section on old workflows above.

Can you automate a SharePoint list without a new licence?

That depends on your Microsoft plan. We check what your plan includes before we build, and we tell you plainly if a job needs something it does not include.

Can you tidy up flows someone else built?

Yes. We list each flow, what it does and whether it still runs. Anything that looks unused is put to you for a decision, and we do not switch off or delete anything without your say.

Can AI help read and file documents?

Often, with a person approving anything unclear. See document automation. We check the data settings and terms first.

Can you build a small app on our lists?

That is usually done with the Power Platform. See the Power Platform page.

Do you run SharePoint for us?

No. SharePoint stays in your own account. We build and repair, then hand over, and you stay in control of access.

Explore more

Related AI automation pages and services

AI Automation (the whole subject) →

All our AI automation services, workflows, platforms and guides in one place.

Microsoft Power Automate consultant →

Flows inside your Microsoft 365 account.

Microsoft Power Platform consultant →

Apps, flows and data for Microsoft 365 businesses.

Document automation →

Read, sort and file documents without retyping.

Microsoft Copilot consultant →

Copilot set up on your own Microsoft 365 licences.

Workflow and business process automation →

For whole processes with several people and approvals.

See all services

Tell us about your business

Tell us about your SharePoint tasks

Describe what is done by hand today, or what you want SharePoint to do. We will tell you the clearest next step, in plain English.

Call 03 4158 4444info@truenorthinnovations.com.au

AI automation work is scoped individually.

We use your details to respond to your enquiry. Read our Privacy Policy.