TAC HRTAC HR
A man seated at a long meeting table facing a wall screen showing blurred participants
Microsoft Teams
Hiring and communicationSigned webhooks

Integration with Microsoft Teams: HR Approvals in Your Team Channels

The integration with Microsoft Teams in TAC HR carries HR decisions into your team's channels. TAC HR sends signed events when a request is approved or rejected, when an employee joins or leaves, and when payroll is paid, to an endpoint your company defines, and your developer or vendor turns them into Teams messages.

01Overview

Requirements

What does your company get from the Teams integration?

  • Decisions where work happens: if your team lives in Teams, the decision reaches them there.
  • Less switching between screens: a manager learns a request's outcome from the channel and opens TAC HR only if they need the details.
  • Coordination at hiring and exit: a new or ended employee event alerts IT and facilities.
  • Awareness of payroll: a "payroll paid" event for the finance channel.

Operational example

A group with two branches uses Teams for internal communication. Its developer builds an endpoint that posts request events in the HR channel. A leave request is rejected in one branch, the rejection message reaches the channel, and the manager contacts the employee to explain the reason.

02What syncs

Where your data lands

What does the integration build on?

  • Signed webhooksfor these events: new or ended employee, approved or rejected request, payroll paid, rejected punch.
  • A read-only APIwith scoped keys, for anyone who wants to read permitted data.

Turning an event into a Teams message is work your technical team sets up.

How does it fit a company with branches?

A TAC HR user sees the data of their branch and department according to their permissions. Your team can route events to a channel per branch when it sets up the endpoint.

When does the integration help most?

  • When the organization lives in Teams dailydecisions reach where the team is waiting.
  • When you have an in-house developerthey set up the endpoint once and reuse it for several events.
  • When you need a weekly reviewapprovals gather in one channel that is easy to revisit.
  • When permissions are separatedeach TAC HR user sees only what their permissions allow.
03Setup steps

The setup, start to finish

Five steps from the system's own screens. What happens outside it, such as uploading a file or loading it into another system, is in your company's hands.

  1. 1Open the Webhooks tabUnder “Settings → Integrations” open the Webhooks tab.Have your developer or provider prepare an https endpoint that turns the notification into a Teams channel message.
  2. 2Choose the approval eventsUnder “New subscription” enter the endpoint address and pick, for example, “request approved” and “request rejected”.You can add “employee created” and “payroll paid” too.
  3. 3Copy the signing secretThe secret shows once: “copy it now, it will not be shown again”.Your developer keeps it at the receiving endpoint to verify the source.
  4. 4Verify the signature, then relayEvery notification is signed with the time, and the receiver rejects anything past the five-minute window.What passes is posted by your endpoint to the channel you choose.
  5. 5Watch the deliveries“Latest deliveries” shows the event, the status, the attempts and the response.You disable or enable the subscription under “Controls” if you want to pause it.
04FAQ

Asked before implementation

Which events are available?

New or ended employee, approved or rejected request, payroll paid and rejected punch.

Can I read data instead of receiving events?

Yes, through the read API with scoped keys.

Is our data isolated?

Yes. Each company's data is isolated from every other company.

Ready to integrate?

Start with one channel

Request a demo to see events and approvals, and read about employee requests and pricing.