In this article we show you how to setup the integration between Tātou and Keypay.
This is a technical article.
Currently, the native integration is composed by three main parts:
Entity | Description | Direction |
|---|---|---|
Employee | Creating, updating or deleting* an employee in Keypay automatically does the same in Tātou * Deleting makes the employee inactive in Tātou | Keypay → Tātou |
PayPeriod | Timesheet entries for a period | Tātou → Keypay |
PayEarning | When the Pay Run is finished in Keypay, it sends the awards interpretation with final costs back to Tātou | Keypay → Tātou |
In order to enable the integration, it’s necessary to create webhooks for each entity. They should be created in the origin platform, see direction above.
Default webhook configuration
To be able to authenticate with the foreign Rest API, all webhooks should contain access tokens for both platforms. On Keypay you should set it as webhook properties and on Tātou as webhook request params:
{
"tatou_token": <token>,
"keypay_token": <token>,
"keypay_business_id": <id>
}
Webhook reference documentation:
Tatou webhook <<< Add link
Data gap between platforms
Every platform has a different approach for dealing with data structure. In order to fill this gap we created lambda functions, so when creating webhooks you should point them to these functions. Functions are available under the subdomain https://integration.tatou.app/{stage}/keypay/{end-point}.
Available stages: dev, staging, production.
Available end points: employee, pay-period, pay-earnings.
Employee integration
Pay Period integration
Pay Earnings integration
Add Comment