Skills publicadas
Mostrando 12 de 543homerun-hr
Homerun HR integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Homerun HR. Routes through Apideck with serviceId "homerun-hr".
microsoft-dynamics-hr
Microsoft Dynamics 365 Human Resources integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Microsoft Dynamics 365 Human Resources. Routes through Apideck with serviceId "microsoft-dynamics-hr".
namely
Namely integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Namely. Routes through Apideck with serviceId "namely".
apideck-php
Apideck Unified API integration patterns for PHP. Use when building integrations with accounting software (QuickBooks, Xero, NetSuite), CRMs (Salesforce, HubSpot, Pipedrive), HRIS platforms (Workday, BambooHR), file storage (Google Drive, Dropbox, Box), ATS systems (Greenhouse, Lever), e-commerce, or any of Apideck's 200+ connectors using PHP. Covers the apideck-libraries/sdk-php Composer package,
xero
Xero integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Xero. Routes through Apideck with serviceId "xero".
sesamehr
Sesame HR via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Sesame HR's native API. Use when the user wants to call Sesame HR (no unified API resource mapping). Routes through Apideck with serviceId "sesamehr".
rillet
Rillet integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Rillet. Routes through Apideck with serviceId "rillet".
mrisoftware
MRI Software integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in MRI Software. Routes through Apideck with serviceId "mrisoftware".
breathehr
Breathe HR integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Breathe HR. Routes through Apideck with serviceId "breathehr".
sympa
Sympa integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Sympa. Routes through Apideck with serviceId "sympa".
google-workspace
Google Workspace integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Google Workspace. Routes through Apideck with serviceId "google-workspace".
jira
Jira integration via Apideck's Issue Tracking unified API — same methods work across every connector in Issue Tracking, switch by changing `serviceId`. Use when the user wants to read, write, or comment on tickets and issues in Jira. Routes through Apideck with serviceId "jira".