all publishers

apideck-libraries

@apideck-libraries source repo

338 published skills · page 1 of 4

  1. ▌
    Blackbaud 2 · apideck-libraries bundle
    Blackbaud 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 Blackbaud. Routes through Apideck with serviceId "blackbaud".
    11 installs
  2. ▌
    Breathehr 2 · apideck-libraries bundle
    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".
    6 installs
  3. ▌
    Cezannehr 2 · apideck-libraries bundle
    Cezanne 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 Cezanne HR. Routes through Apideck with serviceId "cezannehr".
    7 installs
  4. ▌
    Charliehr 2 · apideck-libraries bundle
    CharlieHR 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 CharlieHR. Routes through Apideck with serviceId "charliehr".
    9 installs
  5. ▌
    Dualentry 2 · apideck-libraries bundle
    Dualentry 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 Dualentry. Routes through Apideck with serviceId "dualentry".
    7 installs
  6. ▌
    Freeagent 2 · apideck-libraries bundle
    FreeAgent 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 FreeAgent. Routes through Apideck with serviceId "freeagent".
    5 installs
  7. ▌
    Freshteam 2 · apideck-libraries bundle
    Freshteam 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 Freshteam. Routes through Apideck with serviceId "freshteam".
    6 installs
  8. ▌
    Jumpcloud 2 · apideck-libraries bundle
    JumpCloud 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 JumpCloud. Routes through Apideck with serviceId "jumpcloud".
    11 installs
  9. ▌
    Justworks 2 · apideck-libraries bundle
    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".
    10 installs
  10. ▌
    Moneybird 2 · apideck-libraries bundle
    Moneybird 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 Moneybird. Routes through Apideck with serviceId "moneybird".
    10 installs
  11. ▌
    Paylocity 2 · apideck-libraries bundle
    Paylocity 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 Paylocity. Routes through Apideck with serviceId "paylocity".
    9 installs
  12. ▌
    Pennylane 2 · apideck-libraries bundle
    Pennylane 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 Pennylane. Routes through Apideck with serviceId "pennylane".
    4 installs
  13. ▌
    People Hr 2 · apideck-libraries bundle
    People 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 People HR. Routes through Apideck with serviceId "people-hr".
    7 installs
  14. ▌
    Pipedrive 2 · apideck-libraries bundle
    Pipedrive 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 Pipedrive. Routes through Apideck with serviceId "pipedrive".
    10 installs
  15. ▌
    Recruitee 2 · apideck-libraries bundle
    Recruitee 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 Recruitee. Routes through Apideck with serviceId "recruitee".
    7 installs
  16. ▌
    Cascade Hr 2 · apideck-libraries bundle
    IRIS Cascade 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 IRIS Cascade HR. Routes through Apideck with serviceId "cascade-hr".
    11 installs
  17. ▌
    Freshbooks 2 · apideck-libraries bundle
    FreshBooks 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 FreshBooks. Routes through Apideck with serviceId "freshbooks".
    8 installs
  18. ▌
    Freshsales 2 · apideck-libraries bundle
    Freshworks 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 Freshworks CRM. Routes through Apideck with serviceId "freshsales".
    10 installs
  19. ▌
    Greenhouse 2 · apideck-libraries bundle
    Greenhouse 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 Greenhouse. Routes through Apideck with serviceId "greenhouse".
    6 installs
  20. ▌
    Homerun Hr 2 · apideck-libraries bundle
    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".
    15 installs
  21. ▌
    Humaans Io 2 · apideck-libraries bundle
    Humaans 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 Humaans. Routes through Apideck with serviceId "humaans-io".
    6 installs
  22. ▌
    Jira Teams 2 · apideck-libraries
    Jira Teams via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Jira Teams's native API. Use when the user wants to call Jira Teams (no unified API resource mapping). Routes through Apideck with serviceId "jira-teams".
    8 installs
  23. ▌
    Lightspeed 2 · apideck-libraries bundle
    Lightspeed 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. Routes through Apideck with serviceId "lightspeed".
    6 installs
  24. ▌
    Prestashop 2 · apideck-libraries bundle
    Prestashop 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 Prestashop. Routes through Apideck with serviceId "prestashop".
    10 installs
  25. ▌
    Quickbooks 2 · apideck-libraries bundle
    QuickBooks 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 QuickBooks. Routes through Apideck with serviceId "quickbooks".
    8 installs
  26. ▌
    Salesflare 2 · apideck-libraries bundle
    Salesflare 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 Salesflare. Routes through Apideck with serviceId "salesflare".
    13 installs
  27. ▌
    Salesforce 2 · apideck-libraries bundle
    Salesforce 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 Salesforce. Routes through Apideck with serviceId "salesforce".
    10 installs
  28. ▌
    Servicenow 2 · apideck-libraries
    ServiceNow via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to ServiceNow's native API. Use when the user wants to call ServiceNow (no unified API resource mapping). Routes through Apideck with serviceId "servicenow".
    8 installs
  29. ▌
    Sharepoint 2 · apideck-libraries bundle
    SharePoint 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 SharePoint. Routes through Apideck with serviceId "sharepoint".
    5 installs
  30. ▌
    Teamleader 2 · 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".
    7 installs
  31. ▌
    Teamtailor 2 · 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".
    6 installs
  32. ▌
    Zoho Books 2 · 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".
    7 installs
  33. ▌
    Apideck MCP 2 · apideck-libraries
    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
  34. ▌
    Bigcommerce 2 · 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".
    7 installs
  35. ▌
    Catalystone 2 · 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".
    8 installs
  36. ▌
    Factorialhr 2 · 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".
    10 installs
  37. ▌
    Mrisoftware 2 · apideck-libraries bundle
    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".
    7 installs
  38. ▌
    Woocommerce 2 · apideck-libraries bundle
    WooCommerce 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 WooCommerce. Routes through Apideck with serviceId "woocommerce".
    6 installs
  39. ▌
    Zoho People 2 · apideck-libraries bundle
    Zoho People 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 Zoho People. Routes through Apideck with serviceId "zoho-people".
    4 installs
  40. ▌
    Azure Devops 2 · apideck-libraries
    Azure DevOps via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Azure DevOps's native API. Use when the user wants to call Azure DevOps (no unified API resource mapping). Routes through Apideck with serviceId "azure-devops".
    11 installs
  41. ▌
    Bullhorn Ats 2 · apideck-libraries bundle
    Bullhorn ATS 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 Bullhorn ATS. Routes through Apideck with serviceId "bullhorn-ats".
    10 installs
  42. ▌
    Exact Online 2 · apideck-libraries bundle
    Exact Online 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 Exact Online. Routes through Apideck with serviceId "exact-online".
    6 installs
  43. ▌
    Google Drive 2 · apideck-libraries bundle
    Google Drive 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 Google Drive. Routes through Apideck with serviceId "google-drive".
    8 installs
  44. ▌
    Officient Io 2 · apideck-libraries bundle
    Officient 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 Officient. Routes through Apideck with serviceId "officient-io".
    6 installs
  45. ▌
    Sage Intacct 2 · apideck-libraries bundle
    Sage Intacct 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 Intacct. Routes through Apideck with serviceId "sage-intacct".
    9 installs
  46. ▌
    Zendesk Sell 2 · apideck-libraries bundle
    Zendesk Sell 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 Zendesk Sell. Routes through Apideck with serviceId "zendesk-sell".
    6 installs
  47. ▌
    Clearbooks Uk 2 · apideck-libraries bundle
    Clear 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 Clear Books. Routes through Apideck with serviceId "clearbooks-uk".
    10 installs
  48. ▌
    Gitlab Server 2 · apideck-libraries bundle
    GitLab server (on-prem) 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 server (on-prem). Routes through Apideck with serviceId "gitlab-server".
    6 installs
  49. ▌
    Procountor Fi 2 · apideck-libraries bundle
    Procountor 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 Procountor. Routes through Apideck with serviceId "procountor-fi".
    6 installs
  50. ▌
    Activecampaign 2 · apideck-libraries bundle
    ActiveCampaign 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 ActiveCampaign. Routes through Apideck with serviceId "activecampaign".
    8 installs
  51. ▌
    Employmenthero 2 · apideck-libraries bundle
    Employment Hero 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 Employment Hero. Routes through Apideck with serviceId "employmenthero".
    6 installs
  52. ▌
    Myob Acumatica 2 · apideck-libraries bundle
    MYOB 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 MYOB Acumatica. Routes through Apideck with serviceId "myob-acumatica".
    6 installs
  53. ▌
    Visma Netvisor 2 · apideck-libraries bundle
    Visma Netvisor 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 Visma Netvisor. Routes through Apideck with serviceId "visma-netvisor".
    6 installs
  54. ▌
    Exact Online Nl 2 · apideck-libraries bundle
    Exact Online NL 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 Exact Online NL. Routes through Apideck with serviceId "exact-online-nl".
    10 installs
  55. ▌
    Exact Online Uk 2 · apideck-libraries bundle
    Exact Online UK 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 Exact Online UK. Routes through Apideck with serviceId "exact-online-uk".
    11 installs
  56. ▌
    Google Contacts 2 · apideck-libraries bundle
    Google Contacts 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 Google Contacts. Routes through Apideck with serviceId "google-contacts".
    11 installs
  57. ▌
    Cegid Talentsoft 2 · apideck-libraries bundle
    Cegid Talentsoft 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 Cegid Talentsoft. Routes through Apideck with serviceId "cegid-talentsoft".
    4 installs
  58. ▌
    Google Workspace 2 · apideck-libraries bundle
    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".
    10 installs
  59. ▌
    Jira Data Center 2 · apideck-libraries
    Jira Data Center via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Jira Data Center's native API. Use when the user wants to call Jira Data Center (no unified API resource mapping). Routes through Apideck with serviceId "jira-data-center".
    11 installs
  60. ▌
    Access Financials 2 · 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
  61. ▌
    Adp Workforce Now 2 · 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".
    4 installs
  62. ▌
    Ceridian Dayforce 2 · 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".
    11 installs
  63. ▌
    Jira Service Desk 2 · apideck-libraries
    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".
    11 installs
  64. ▌
    Microsoft Outlook 2 · 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".
    9 installs
  65. ▌
    Sage Intacct REST 2 · apideck-libraries
    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".
    12 installs
  66. ▌
    Sdworx Webservice 2 · 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".
    7 installs
  67. ▌
    Jetbrains Youtrack 2 · apideck-libraries
    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".
    8 installs
  68. ▌
    Microsoft Dynamics 2 · 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".
    8 installs
  69. ▌
    Sap Successfactors 2 · 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".
    10 installs
  70. ▌
    Shopify Public App 2 · 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".
    4 installs
  71. ▌
    Apideck Unified API 2 · apideck-libraries
    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.).
    11 installs
  72. ▌
    Apideck MCP Pay Bill 2 · apideck-libraries
    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.
    13 installs
  73. ▌
    Lightspeed Ecommerce 2 · 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
  74. ▌
    Amazon Seller Central 2 · 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".
    7 installs
  75. ▌
    Linear Multiworkspace 2 · 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".
    4 installs
  76. ▌
    Microsoft Dynamics Hr 2 · 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".
    6 installs
  77. ▌
    Azure Active Directory 2 · 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".
    9 installs
  78. ▌
    Intuit Enterprise Suite 2 · 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".
    5 installs
  79. ▌
    Apideck MCP Month End Close 2 · apideck-libraries
    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.
    10 installs
  80. ▌
    Apideck MCP Receive Payment 2 · apideck-libraries
    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.
    13 installs
  81. ▌
    Apideck MCP Onboard Employee 2 · 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.
    11 installs
  82. ▌
    Sage Business Cloud Accounting 2 · 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".
    9 installs
  83. ▌
    Microsoft Dynamics 365 Business Central 2 · 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".
    6 installs
  84. ▌
    Act 2 · apideck-libraries bundle
    Act 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 Act. Routes through Apideck with serviceId "act".
    9 installs
  85. ▌
    Box 2 · apideck-libraries bundle
    Box 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 Box. Routes through Apideck with serviceId "box".
    10 installs
  86. ▌
    Wix 2 · apideck-libraries bundle
    Wix 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 Wix . Routes through Apideck with serviceId "wix".
    6 installs
  87. ▌
    Afas 2 · apideck-libraries bundle
    AFAS Software 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 AFAS Software. Routes through Apideck with serviceId "afas".
    7 installs
  88. ▌
    Deel 2 · apideck-libraries bundle
    Deel 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 Deel. Routes through Apideck with serviceId "deel".
    8 installs
  89. ▌
    Ebay 2 · apideck-libraries bundle
    eBay 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 eBay. Routes through Apideck with serviceId "ebay".
    8 installs
  90. ▌
    Etsy 2 · apideck-libraries bundle
    Etsy 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 Etsy. Routes through Apideck with serviceId "etsy".
    5 installs
  91. ▌
    Folk 2 · apideck-libraries bundle
    Folk 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 Folk. Routes through Apideck with serviceId "folk".
    7 installs
  92. ▌
    Jira 2 · apideck-libraries bundle
    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".
    5 installs
  93. ▌
    Keka 2 · apideck-libraries bundle
    Keka 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 Keka HR. Routes through Apideck with serviceId "keka".
    11 installs
  94. ▌
    Myob 2 · apideck-libraries bundle
    MYOB 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 MYOB. Routes through Apideck with serviceId "myob".
    7 installs
  95. ▌
    Odoo 2 · apideck-libraries bundle
    Odoo integration via Apideck's CRM, Accounting unified API — same methods work across every connector in CRM, Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in Odoo. Routes through Apideck with serviceId "odoo".
    6 installs
  96. ▌
    Okta 2 · apideck-libraries bundle
    Okta 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 Okta. Routes through Apideck with serviceId "okta".
    8 installs
  97. ▌
    Wave 2 · apideck-libraries bundle
    Wave 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 Wave. Routes through Apideck with serviceId "wave".
    7 installs
  98. ▌
    Xero 2 · apideck-libraries bundle
    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".
    10 installs
  99. ▌
    Yuki 2 · apideck-libraries bundle
    Yuki 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 Yuki. Routes through Apideck with serviceId "yuki".
    9 installs
  100. ▌
    Asana 2 · apideck-libraries
    Asana via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Asana's native API. Use when the user wants to call Asana (no unified API resource mapping). Routes through Apideck with serviceId "asana".
    7 installs