apideck-libraries

Task playbook for converting a hired ATS applicant into an HRIS employee via the Apideck MCP server's `apideck-onboard-employee` workflow tool. First cross-unified-API workflow — requires both ATS and HRIS connections active on the consumer. Optionally moves the applicant to a "hired" stage in the ATS to close the loop.

Paychex 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 Paychex. Routes through Apideck with serviceId "paychex".

SAP SuccessFactors integration via Apideck's HRIS, ATS unified API — same methods work across every connector in HRIS, ATS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in SAP SuccessFactors. Routes through Apideck with serviceId "sap-successfactors".

Lever integration via Apideck's ATS unified API — same methods work across every connector in ATS, switch by changing `serviceId`. Use when the user wants to read, write, or sync jobs, applicants, and applications in Lever. Routes through Apideck with serviceId "lever".

Holded 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 Holded. Routes through Apideck with serviceId "holded".

Ceridian Dayforce 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 Ceridian Dayforce. Routes through Apideck with serviceId "ceridian-dayforce".

Workday integration via Apideck's Accounting, HRIS, ATS unified API — same methods work across every connector in Accounting, HRIS, ATS, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Workday. Routes through Apideck with serviceId "workday".

GitLab 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 GitLab. Routes through Apideck with serviceId "gitlab".

HubSpot integration via Apideck's CRM unified API — same methods work across every connector in CRM, switch by changing `serviceId`. Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in HubSpot. Routes through Apideck with serviceId "hubspot".

Mollie via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Mollie's native API. Use when the user wants to call Mollie (no unified API resource mapping). Routes through Apideck with serviceId "mollie".

Justworks 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 Justworks. Routes through Apideck with serviceId "justworks".

Apideck Unified API integration patterns for Go. 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 Go. Covers the github.com/apideck-libraries/sdk-go package,