← all publishers

apideck-libraries

@apideck-libraries source repo

Report this profile Claim this profile

• 338 skills
• 0 followers
• last month last updated

1. ▌
   Attio 2 · apideck-libraries bundle

   Attio 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 Attio. Routes through Apideck with serviceId "attio".
   9 installs
2. ▌
   Ciphr 2 · apideck-libraries bundle

   CIPHR 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 CIPHR. Routes through Apideck with serviceId "ciphr".
   3 installs
3. ▌
   Close 2 · apideck-libraries bundle

   Close 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 Close. Routes through Apideck with serviceId "close".
   6 installs
4. ▌
   Hibob 2 · apideck-libraries bundle

   Hibob 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 Hibob. Routes through Apideck with serviceId "hibob".
   8 installs
5. ▌
   Kenjo 2 · apideck-libraries bundle

   Kenjo 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 Kenjo. Routes through Apideck with serviceId "kenjo".
   6 installs
6. ▌
   Lever 2 · apideck-libraries bundle

   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".
   10 installs
7. ▌
   Nmbrs 2 · apideck-libraries bundle

   Visma Nmbrs 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 Visma Nmbrs. Routes through Apideck with serviceId "nmbrs".
   9 installs
8. ▌
   Sympa 2 · apideck-libraries bundle

   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".
   5 installs
9. ▌
   Acerta 2 · apideck-libraries bundle

   Acerta 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 Acerta. Routes through Apideck with serviceId "acerta".
   6 installs
10. ▌
    Banqup 2 · apideck-libraries bundle

    banqUP 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 banqUP. Routes through Apideck with serviceId "banqup".
    8 installs
11. ▌
    Copper 2 · apideck-libraries bundle

    Copper 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 Copper. Routes through Apideck with serviceId "copper".
    5 installs
12. ▌
    Digits 2 · apideck-libraries bundle

    Digits 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 Digits. Routes through Apideck with serviceId "digits".
    5 installs
13. ▌
    Fourth 2 · apideck-libraries bundle

    Fourth 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 Fourth. Routes through Apideck with serviceId "fourth".
    9 installs
14. ▌
    Github 2 · apideck-libraries bundle

    GitHub 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 GitHub. Routes through Apideck with serviceId "github".
    10 installs
15. ▌
    Gitlab 2 · apideck-libraries bundle

    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".
    5 installs
16. ▌
    Holded 2 · apideck-libraries bundle

    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".
    10 installs
17. ▌
    Linear 2 · apideck-libraries bundle

    Linear 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 Linear. Routes through Apideck with serviceId "linear".
    7 installs
18. ▌
    Mollie 2 · apideck-libraries

    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".
    8 installs
19. ▌
    Monday 2 · apideck-libraries

    monday.com via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to monday.com's native API. Use when the user wants to call monday.com (no unified API resource mapping). Routes through Apideck with serviceId "monday".
    5 installs
20. ▌
    Namely 2 · apideck-libraries bundle

    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".
    7 installs
21. ▌
    Notion 2 · apideck-libraries

    Notion via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Notion's native API. Use when the user wants to call Notion (no unified API resource mapping). Routes through Apideck with serviceId "notion".
    6 installs
22. ▌
    Payfit 2 · apideck-libraries bundle

    PayFit 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 PayFit. Routes through Apideck with serviceId "payfit".
    5 installs
23. ▌
    Picqer 2 · apideck-libraries bundle

    Picqer integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in Picqer. Routes through Apideck with serviceId "picqer".
    4 installs
24. ▌
    Remote 2 · apideck-libraries bundle

    Remote 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 Remote. Routes through Apideck with serviceId "remote".
    8 installs
25. ▌
    Rillet 2 · apideck-libraries bundle

    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".
    9 installs
26. ▌
    Sdworx 2 · apideck-libraries bundle

    SD Worx 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 SD Worx. Routes through Apideck with serviceId "sdworx".
    8 installs
27. ▌
    Stripe 2 · apideck-libraries bundle

    Stripe 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 Stripe. Routes through Apideck with serviceId "stripe".
    6 installs
28. ▌
    Tiktok 2 · apideck-libraries bundle

    TikTok Shop integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in TikTok Shop. Routes through Apideck with serviceId "tiktok".
    5 installs
29. ▌
    Trinet 2 · apideck-libraries bundle

    TriNet 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 TriNet. Routes through Apideck with serviceId "trinet".
    5 installs
30. ▌
    Adp Run 2 · apideck-libraries bundle

    RUN Powered by ADP 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 RUN Powered by ADP. Routes through Apideck with serviceId "adp-run".
    5 installs
31. ▌
    Bol Com 2 · apideck-libraries bundle

    bol.com integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in bol.com. Routes through Apideck with serviceId "bol-com".
    7 installs
32. ▌
    Clickup 2 · apideck-libraries

    ClickUp via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to ClickUp's native API. Use when the user wants to call ClickUp (no unified API resource mapping). Routes through Apideck with serviceId "clickup".
    3 installs
33. ▌
    Dropbox 2 · apideck-libraries bundle

    Dropbox integration via Apideck's File Storage unified API — same methods work across every connector in File Storage, switch by changing `serviceId`. Use when the user wants to read, write, upload, or search files, folders, and drives in Dropbox. Routes through Apideck with serviceId "dropbox".
    5 installs
34. ▌
    Hubspot 2 · apideck-libraries bundle

    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".
    5 installs
35. ▌
    Liantis 2 · apideck-libraries bundle

    Liantis 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 Liantis. Routes through Apideck with serviceId "liantis".
    5 installs
36. ▌
    Magento 2 · apideck-libraries bundle

    Magento integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in Magento. Routes through Apideck with serviceId "magento".
    7 installs
37. ▌
    Paychex 2 · apideck-libraries bundle

    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".
    8 installs
38. ▌
    Planhat 2 · apideck-libraries bundle

    Planhat 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 Planhat. Routes through Apideck with serviceId "planhat".
    7 installs
39. ▌
    Sage Hr 2 · apideck-libraries bundle

    Sage HR 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 Sage HR. Routes through Apideck with serviceId "sage-hr".
    8 installs
40. ▌
    Sapling 2 · apideck-libraries bundle

    Sapling 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 Sapling. Routes through Apideck with serviceId "sapling".
    6 installs
41. ▌
    Shopify 2 · apideck-libraries bundle

    Shopify integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in Shopify. Routes through Apideck with serviceId "shopify".
    5 installs
42. ▌
    Ukg Pro 2 · apideck-libraries bundle

    UKG Pro 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 UKG Pro. Routes through Apideck with serviceId "ukg-pro".
    6 installs
43. ▌
    Walmart 2 · apideck-libraries bundle

    Walmart integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in Walmart. Routes through Apideck with serviceId "walmart".
    5 installs
44. ▌
    Workday 2 · apideck-libraries bundle

    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".
    9 installs
45. ▌
    Zendesk 2 · apideck-libraries

    Zendesk via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Zendesk's native API. Use when the user wants to call Zendesk (no unified API resource mapping). Routes through Apideck with serviceId "zendesk".
    7 installs
46. ▌
    Adp Ihcm 2 · apideck-libraries bundle

    ADP iHCM 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 ADP iHCM. Routes through Apideck with serviceId "adp-ihcm".
    5 installs
47. ▌
    Alexishr 2 · apideck-libraries bundle

    Simployer One 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 Simployer One. Routes through Apideck with serviceId "alexishr".
    9 installs
48. ▌
    Bamboohr 2 · apideck-libraries bundle

    BambooHR 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 BambooHR. Routes through Apideck with serviceId "bamboohr".
    8 installs
49. ▌
    Basecamp 2 · apideck-libraries

    Basecamp via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Basecamp's native API. Use when the user wants to call Basecamp (no unified API resource mapping). Routes through Apideck with serviceId "basecamp".
    6 installs
50. ▌
    Campfire 2 · apideck-libraries bundle

    Campfire 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 Campfire. Routes through Apideck with serviceId "campfire".
    6 installs
51. ▌
    Flexmail 2 · apideck-libraries bundle

    Flexmail 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 Flexmail. Routes through Apideck with serviceId "flexmail".
    6 installs
52. ▌
    Folks Hr 2 · apideck-libraries bundle

    Folks 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 Folks HR. Routes through Apideck with serviceId "folks-hr".
    10 installs
53. ▌
    Hr Works 2 · apideck-libraries bundle

    HR Works 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 HR Works. Routes through Apideck with serviceId "hr-works".
    6 installs
54. ▌
    Intercom 2 · apideck-libraries

    Intercom via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Intercom's native API. Use when the user wants to call Intercom (no unified API resource mapping). Routes through Apideck with serviceId "intercom".
    6 installs
55. ▌
    Jobadder 2 · apideck-libraries bundle

    JobAdder 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 JobAdder. Routes through Apideck with serviceId "jobadder".
    8 installs
56. ▌
    Kashflow 2 · apideck-libraries bundle

    Kashflow 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 Kashflow. Routes through Apideck with serviceId "kashflow".
    8 installs
57. ▌
    Loket Nl 2 · apideck-libraries bundle

    Loket.nl 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 Loket.nl. Routes through Apideck with serviceId "loket-nl".
    5 installs
58. ▌
    Lucca Hr 2 · apideck-libraries bundle

    Lucca 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 Lucca. Routes through Apideck with serviceId "lucca-hr".
    6 installs
59. ▌
    Netsuite 2 · apideck-libraries bundle

    NetSuite 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 NetSuite. Routes through Apideck with serviceId "netsuite".
    5 installs
60. ▌
    Onedrive 2 · apideck-libraries bundle

    OneDrive integration via Apideck's File Storage unified API — same methods work across every connector in File Storage, switch by changing `serviceId`. Use when the user wants to read, write, upload, or search files, folders, and drives in OneDrive. Routes through Apideck with serviceId "onedrive".
    6 installs
61. ▌
    Onelogin 2 · apideck-libraries bundle

    OneLogin 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 OneLogin. Routes through Apideck with serviceId "onelogin".
    1 install
62. ▌
    Personio 2 · apideck-libraries bundle

    Personio 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 Personio. Routes through Apideck with serviceId "personio".
    5 installs
63. ▌
    Sesamehr 2 · apideck-libraries

    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".
    10 installs
64. ▌
    Shopware 2 · apideck-libraries bundle

    Shopware integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in Shopware. Routes through Apideck with serviceId "shopware".
    5 installs
65. ▌
    Shortcut 2 · apideck-libraries

    Shortcut via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Shortcut's native API. Use when the user wants to call Shortcut (no unified API resource mapping). Routes through Apideck with serviceId "shortcut".
    8 installs
66. ▌
    Silae Fr 2 · apideck-libraries bundle

    Silae 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 Silae. Routes through Apideck with serviceId "silae-fr".
    7 installs
67. ▌
    Workable 2 · apideck-libraries bundle

    Workable 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 Workable. Routes through Apideck with serviceId "workable".
    5 installs
68. ▌
    Zoho Crm 2 · apideck-libraries bundle

    Zoho CRM 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 Zoho CRM. Routes through Apideck with serviceId "zoho-crm".
    5 installs
69. ▌
    Acumatica 2 · apideck-libraries bundle

    Acumatica 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 Acumatica. Routes through Apideck with serviceId "acumatica".
    8 installs
70. ▌
    Microsoft Dynamics Hr · apideck-libraries bundle

    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".
    8 installs
71. ▌
    Azure Active Directory · apideck-libraries bundle

    Microsoft Entra 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 Entra. Routes through Apideck with serviceId "azure-active-directory".
    8 installs
72. ▌
    Intuit Enterprise Suite · apideck-libraries bundle

    Intuit Enterprise Suite 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 Intuit Enterprise Suite. Routes through Apideck with serviceId "intuit-enterprise-suite".
    10 installs
73. ▌
    Apideck MCP Month End Close · apideck-libraries bundle

    Task playbook for fetching a month-end financial snapshot via the Apideck MCP server's `apideck-month-end-close-check` workflow tool. Use when the user asks for a P&L, balance sheet, aged creditors, or aged debtors view at a point in time. Read-only, idempotent, returns partial snapshots when some reports aren't supported by the connector.
    11 installs
74. ▌
    Apideck MCP Receive Payment · apideck-libraries bundle

    Task playbook for recording a customer payment against an invoice via the Apideck MCP server's `apideck-receive-customer-payment` workflow tool. Use when the user says a customer paid an invoice and wants the accounting service updated. AR mirror of `apideck-pay-bill` — same shape, opposite ledger side. Different unified endpoint, different counterparty (customer vs supplier), different allocation type.
    10 installs
75. ▌
    Apideck MCP Onboard Employee · apideck-libraries bundle

    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.
    11 installs
76. ▌
    Sage Business Cloud Accounting · apideck-libraries bundle

    Sage Business Cloud Accounting 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 Sage Business Cloud Accounting. Routes through Apideck with serviceId "sage-business-cloud-accounting".
    11 installs
77. ▌
    Microsoft Dynamics 365 Business Central · apideck-libraries bundle

    Microsoft Dynamics 365 Business Central 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 Microsoft Dynamics 365 Business Central. Routes through Apideck with serviceId "microsoft-dynamics-365-business-central".
    8 installs
78. ▌
    Access Financials · apideck-libraries bundle

    Access Financials 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 Access Financials. Routes through Apideck with serviceId "access-financials".
    6 installs
79. ▌
    Adp Workforce Now · apideck-libraries bundle

    ADP Workforce Now 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 ADP Workforce Now. Routes through Apideck with serviceId "adp-workforce-now".
    11 installs
80. ▌
    Ceridian Dayforce · apideck-libraries bundle

    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".
    8 installs
81. ▌
    Jira Service Desk · apideck-libraries bundle

    Jira Service Desk via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Jira Service Desk's native API. Use when the user wants to call Jira Service Desk (no unified API resource mapping). Routes through Apideck with serviceId "jira-service-desk".
    10 installs
82. ▌
    Microsoft Outlook · apideck-libraries bundle

    Microsoft Outlook 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 Microsoft Outlook. Routes through Apideck with serviceId "microsoft-outlook".
    4 installs
83. ▌
    Sage Intacct REST · apideck-libraries bundle

    Sage Intacct REST via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Sage Intacct REST's native API. Use when the user wants to call Sage Intacct REST (no unified API resource mapping). Routes through Apideck with serviceId "sage-intacct-rest".
    10 installs
84. ▌
    Sdworx Webservice · apideck-libraries bundle

    SD Worx (Web service) 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 SD Worx (Web service). Routes through Apideck with serviceId "sdworx-webservice".
    6 installs
85. ▌
    Jetbrains Youtrack · apideck-libraries bundle

    JetBrains YouTrack via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to JetBrains YouTrack's native API. Use when the user wants to call JetBrains YouTrack (no unified API resource mapping). Routes through Apideck with serviceId "jetbrains-youtrack".
    5 installs
86. ▌
    Microsoft Dynamics · apideck-libraries bundle

    Microsoft Dynamics CRM 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 Microsoft Dynamics CRM. Routes through Apideck with serviceId "microsoft-dynamics".
    11 installs
87. ▌
    Sap Successfactors · apideck-libraries bundle

    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".
    8 installs
88. ▌
    Shopify Public App · apideck-libraries bundle

    Shopify (Public App) integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in Shopify (Public App). Routes through Apideck with serviceId "shopify-public-app".
    7 installs
89. ▌
    Apideck Unified API · apideck-libraries bundle

    Apideck Unified API — one set of methods for 146+ SaaS connectors across CRM (21 connectors), Accounting (34), HRIS (58), ATS (11), File Storage (5), Issue Tracking (6), and Ecommerce (17). Route to Salesforce, HubSpot, QuickBooks, Xero, NetSuite, BambooHR, Workday, Greenhouse, SharePoint, Google Drive, Jira, Shopify, and 130+ more by changing a single serviceId string. Use as the starting point whenever the user wants to integrate with a SaaS app — check Apideck coverage first, then use a connector-specific skill (e.g. `salesforce`, `hubspot`) or the language SDK skill (`apideck-node`, `apideck-python`, etc.).
    8 installs
90. ▌
    Apideck MCP Pay Bill · apideck-libraries bundle

    Task playbook for paying a vendor bill via the Apideck MCP server's `apideck-pay-bill` workflow tool. Use when the user asks to settle, pay, or close a known accounts-payable bill in QuickBooks, Xero, NetSuite, or any other connected accounting service. Covers confirmation prompts, partial payments, payment-method capitalization quirks, and the AP-vs-AR routing decision agents routinely get wrong.
    12 installs
91. ▌
    Lightspeed Ecommerce · apideck-libraries bundle

    Lightspeed eCom (C-Series) integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in Lightspeed eCom (C-Series). Routes through Apideck with serviceId "lightspeed-ecommerce".
    6 installs
92. ▌
    Amazon Seller Central · apideck-libraries bundle

    Amazon Seller Central integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in Amazon Seller Central. Routes through Apideck with serviceId "amazon-seller-central".
    5 installs
93. ▌
    Linear Multiworkspace · apideck-libraries bundle

    Linear Multiworkspace 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 Linear Multiworkspace. Routes through Apideck with serviceId "linear-multiworkspace".
    10 installs
94. ▌
    Teamleader · apideck-libraries bundle

    Teamleader 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 Teamleader. Routes through Apideck with serviceId "teamleader".
    10 installs
95. ▌
    Teamtailor · apideck-libraries bundle

    Teamtailor 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 Teamtailor. Routes through Apideck with serviceId "teamtailor".
    9 installs
96. ▌
    Zoho Books · apideck-libraries bundle

    Zoho Books 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 Zoho Books. Routes through Apideck with serviceId "zoho-books".
    5 installs
97. ▌
    Apideck MCP · apideck-libraries bundle

    Front-door skill for the Apideck MCP server — 330 unified-API tools across 10 domains plus 4 intent-grouped workflow tools, exposed via dynamic discovery. Use when the user is building an MCP-based agent (Claude Code, OpenAI Agents SDK, Pydantic AI, LangChain) and wants to integrate with any of the 200+ SaaS connectors Apideck covers. Hosted at mcp.apideck.dev/mcp; stdio transport via `npx -y @apideck/mcp` for local development.
    6 installs
98. ▌
    Bigcommerce · apideck-libraries bundle

    BigCommerce integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in BigCommerce. Routes through Apideck with serviceId "bigcommerce".
    9 installs
99. ▌
    Catalystone · apideck-libraries bundle

    CatalystOne 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 CatalystOne. Routes through Apideck with serviceId "catalystone".
    9 installs
100. ▌
     Factorialhr · apideck-libraries bundle

     Factorial 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 Factorial. Routes through Apideck with serviceId "factorialhr".
     6 installs