Checking…

Outlook add-in

See the sender's company and open tickets in HaloPSA or Autotask, add the email to a ticket, or raise a new one, without leaving Outlook.

Add-in link

https://freepsatools.com/outlook/manifest.xml

Outlook add-ins belong to a mailbox, not to the Outlook app. Every account in Outlook needs the add-in once, either from its Microsoft 365 admin (option A) or added by hand (option B). Using the link rather than a file means updates reach you automatically.

A. For a whole company (recommended)

  1. A Microsoft 365 admin opens admin.microsoft.com → Settings → Integrated apps.
  2. Choose Upload custom apps, then Office Add-in, then Provide link to manifest file, and paste the link above.
  3. Assign it to everyone (or chosen users) and choose Deploy.

It then appears as an admin-managed add-in in every Outlook those users open: new and classic Outlook for Windows, Outlook for Mac, and Outlook on the web. Microsoft says it can take up to 24 hours to show.

B. Just for one mailbox

  1. Go to aka.ms/olksideload, signed in as that mailbox.
  2. Under Custom add-ins choose Add a custom add-in → Add from URL and paste the link above. Or download the file and use Add from file.
  3. Repeat for each account you have in Outlook, then quit and reopen Outlook.

This works for Microsoft 365 and Outlook.com mailboxes. Gmail, iCloud and other IMAP accounts added to Outlook may not run add-ins, because that is up to Microsoft.

HaloPSA: one-off setup by your Halo admin

Each person signs in to Halo as themselves, so there are no shared secrets and every note is recorded under their name. Your admin creates one application for everyone:

  1. In Halo go to Configuration → Integrations → HaloPSA API → View Applications → New.
  2. Name it Outlook add-in. Set Authentication Method to Authorisation Code (Native Application) and Login Type to Agent.
  3. Set Login Redirect URL to https://freepsatools.com/outlook/auth/callback
  4. On Permissions, tick all (or read tickets, clients, users and CRM, and edit tickets and actions).
  5. Save, and give your team the Client ID. There is no secret, and no CORS entry is needed.

In the add-in, choose HaloPSA and enter your Halo URL, tenant (hosted Halo only) and that Client ID, then click Sign in with HaloPSA. It remembers the details, so next time it's one click.

Then connect your PSA

  1. Open any email and click PSA Tickets on the ribbon (or under the … / Apps menu).
  2. HaloPSA: enter your Halo URL and the Client ID from the setup above, then Sign in with HaloPSA. Autotask: enter an API-only user, which is all Autotask's API allows. Sign in once and every account in Outlook on that computer uses it.
  3. Pin the pane so it follows you from email to email.

What it does

  • Matches the sender to a contact by email address, or to a company by email domain
  • Lists that company's open tickets, with a link to open each one in your PSA
  • Adds the email to a ticket as a note. In Halo you choose whether the customer can see it.
  • Creates a new ticket from the email for the matched company and contact
  • Lets you pick the company yourself when the match is wrong

Security

Your PSA credentials are checked, then encrypted by freepsatools.com with a key only the server holds. Outlook keeps only that ciphertext (in the mailbox settings and on this computer) for 30 days. It is never written to a database.

The add-in can only read the email you have open. In Halo every person signs in as themselves. In Autotask notes and tickets are created as the API user, so use a dedicated API-only resource with just the permissions it needs. Sign out in the pane forgets the credentials.