Connect Apps

The catalog of systems you can automate, including the Assignar apps for your operational and commercial data

Connect Apps

What This Feature Does

A Connect App is a ready-made integration: a bundle of triggers and actions for one system, installed and looked after for you. You never deal with technical setup. You pick an app, pick a trigger or an action, and fill in a short form.

Two of those apps are ours, and they put Assignar at the centre of your automations.

Assignar Pay

Works instantly, with no setup and no credentials to find. The connection to your organisation is created automatically and securely the first time you open Connect.

What it can watch for

Assignar Pay triggers fire within seconds of the event, across the records your business runs on:

  • Invoices: created, updated, status changed, deleted. All four can be filtered by Created By Role (who raised the invoice), and all but created by Changed By Role — who last wrote, not who raised it.
  • Timesheets: created, status changed, approval status changed
  • Form submissions: created, updated
  • Purchase orders: created, status changed. Both can be filtered by Created By Role (who raised the order). Purchase Order Status Changed also has Changed By Role — who just moved the status, not who originally raised it.
  • Quotes: created, status changed. Both offer Created By Role; status changed also offers Changed By Role.
  • Supplier invoices: created, status changed. Both offer Created By Role — including Supplier, so a workflow can react when the supplier submits rather than when your team raises the invoice internally. Status changed also offers Changed By Role, which is how you react to "a manager approved this".
  • Workpacks: created, status changed
  • Workpack defects: raised, status changed
  • Dockets: created, status changed
  • Orders: created, status changed
  • Allocations: created, status changed
  • Clients: created, updated
  • Worker tags: tag added to a worker, tag removed from a worker — one event per tag, so a workflow can react to a single tag such as Inducted
  • Tags: created, updated, deleted

Every trigger can be narrowed so it only wakes your workflow for the records you care about. Depending on the record, you can filter by client, project, supplier, worker, tag, form, status, type, a minimum amount, and — on invoices, quotes, purchase orders and supplier invoices — who created it or who just changed its status. Pick a client and the project list narrows to that client's projects, so you are never hunting through a list of every project you have ever run.

A role filter always means the person's current role on the organisation, not the role they held when the record was raised. Someone who has left the organisation never matches, and a record created by an import or an integration key has no role at all, so it never matches either.

Status changes are filtered, not hard-coded. Rather than a separate trigger for each transition, one Status Changed trigger covers them all and you say which move you care about:

  • Leave both From Status and To Status empty to react to every change.
  • Set To Status to Paid for "when an invoice gets paid".
  • Set From Status to Pending and To Status to Overdue for "when an invoice tips into overdue".

Note: if you have used Connect before, you may remember separate Invoice Paid and Timesheet Approved triggers. They have been replaced by the status triggers above, which cover those cases and every other transition too. Use Invoice Status Changed with To Status set to Paid, or Timesheet Approval Status Changed with To Status set to Approved.

What it can do

  • Find records across invoices, timesheets, form submissions, dockets, orders, allocations, purchase orders, quotes, supplier invoices, workpacks, workpack defects, and cost codes, with the same filters, sorting, and date ranges you would use on screen.
  • Fetch one record by its reference, when a workflow already knows which one it needs.
  • Move a record forward: update an invoice status or a purchase order status.
  • Tag a worker: add a tag such as Inducted to a worker, remove one, or replace one with another — for example moving someone from Inducted to Induction Expired when their induction lapses. Name the worker by picking them, by the Assignar Pay user who submitted a form, or by email. Adding a tag the worker already has, or removing one they do not have, is fine, so a workflow can safely run again. Every tag change is recorded in the worker's activity log in Assignar Pay, naming the person the workflow ran as — so you can always see who changed what and when. These steps run as the workspace's Assignar Pay user, who needs permission to manage tags.
  • Reach people: send a document by email, add a comment to a record's activity trail, send an in-app notification to roles or named people, and send a text message to your crew.
  • Ask a person before continuing: Request Approval in Assignar pauses the workflow until someone approves or rejects it in Connect → Approvals, with a permanent record of the decision.
  • Create and produce: create a cost code, or merge a document template with data from your workflow and get a finished PDF back to email, store, or attach.
  • Check your balance: read your remaining SMS credits so a workflow can warn someone before you run out.

Assignar Ops

Connects to your Assignar operations account with the same three details as the integrations page: Region, Client ID, and Client Secret, from your Assignar dashboard under Settings, then API Access. The details are checked the moment you create the connection, so you know immediately that they work.

What it can watch for

Assignar Ops triggers check for new activity every few minutes:

  • New Form Result, which you can pin to a single form so your workflow always gets the same set of questions
  • New Digital Docket
  • New Order and Updated Order
  • New Leave Request
  • Timesheet Created or Updated

What it can do

Find, fetch, create, and update workers, orders, projects, clients, and assets. Read form results and dockets. Create, approve, and decline leave requests. Process timesheets. Pick a client and the project list narrows to that client's projects, the same as in Assignar Pay.

Hundreds of other systems

Alongside the Assignar apps, the catalog covers hundreds of the tools businesses run on: email and calendars, spreadsheets, chat and messaging, cloud storage, customer records, accounting packages, project tools, databases, text messaging, e-signature, and many more. Utility apps handle the glue between them: schedules, delays, branching, and data formatting. For decisions that should stay inside Assignar, use Request Approval in Assignar rather than chat or email approvals.

New apps are added all the time. The catalog you see today is the smallest it will ever be.

Common Tasks

Connecting an outside system for the first time

  1. Add the trigger or action you want.
  2. Click Connect on the connection field.
  3. Sign in to that system, or paste the details it asks for.
  4. The connection is saved for your organisation, so the next workflow that needs it just picks it from the list.

Reusing one connection everywhere

Connections belong to your organisation, not to a single workflow. Set up your email or spreadsheet account once and every future workflow can use it.

Troubleshooting

A connection stopped working

Outside systems sometimes expire the access they gave you, for example after a password change. Open the connection and sign in again. Workflows using it start working again straight away.

I cannot find the system I need

Tell us. If a system matters to your business and there is no app for it yet, contact us with a custom integration request. We give every request serious consideration, and customer requests shape what we build next.

What's Next