Skip to main content
The Zapier SDK is in closed beta. We’re working with a small group of developers and agent builders to shape the SDK before a wider release. Access is free during the beta — try it, break it, tell us what’s missing. Request access
Connect your app, agent, or backend to 8,000+ integrations with a few lines of code. Run actions, manage user connections, and chain apps together. The SDK handles token refresh, retries, and API differences so you can focus on what to build, not how to connect.

For Developers

Build server-side integrations that execute Zapier actions, manage user connections, and automate workflows programmatically.

For Agents

Every team is building agents that talk to APIs. The SDK gives those agents a single integration point to act across 8,000+ apps — no custom connectors required.

​
Key Features

  • 8,000+ App Integrations: Access Zapier’s entire ecosystem of pre-built connectors
  • Type-Safe: Full TypeScript support with generated types for every app and action
  • Simple Authentication: Browser-based login, client credentials, or direct token for seamless auth
  • Paginated Results: Simple pagination and iteration over lists of resources
  • Built-in Actions: Easily call our built-in actions with a simple apps.slack.write.channel_message() syntax.
  • Custom API Requests: Use our fetch method and make authenticated requests to any API through Zapier’s infrastructure to go beyond our built-in actions

​
Get Started

Ready to build? Follow our quickstart guide to run your first action in minutes.

​
What Can You Build?

​
Example Use Case: Reschedule a meeting and notify attendees

Your user says: “Move my 2pm meeting to Thursday and let the attendees know.” Your agent finds the meeting in Google Calendar, reschedules it, and messages each attendee in Slack - all via the SDK: 
import { createZapierSdk } from "@zapier/zapier-sdk";

const zapier = createZapierSdk();

// Bind the user's connected accounts
const { data: calConnection } = await zapier.findFirstConnection({
  appKey: "google-calendar",
  owner: "me",
  isExpired: false,
});
const { data: slackConnection } = await zapier.findFirstConnection({
  appKey: "slack",
  owner: "me",
  isExpired: false,
});

const calendar = zapier.apps.google_calendar({
  connectionId: calConnection.id,
});
const slack = zapier.apps.slack({ connectionId: slackConnection.id });

// Find a specific meeting
const { data: events } = await calendar.search.event_v2({
  inputs: {
    calendarid: "Calendar ID",
    search_term: "Meeting Title",
  },
});
const meeting = events[0] as {
  id: string;
  summary: string;
  attendees: { email: string }[];
};

// Move it to Thursday
await calendar.write.update_event({
  inputs: {
    calendarid: "Calendar ID",
    eventid: meeting.id,
    start__dateTime: "2026-02-19T12:00:00-00:00",
    end__dateTime: "2026-02-19T12:30:00-00:00",
  },
});

// Look up Slack user IDs for all attendees
const slackUsers = await Promise.all(
  meeting.attendees.map((attendee) =>
    slack.search.user_by_email({ inputs: { email: attendee.email } }),
  ),
);

// Notify each attendee via Slack DM
for (const { data } of slackUsers) {
  const user = data[0] as { id: string };
  await slack.write.direct_message({
    inputs: {
      channel: user.id,
      text: `Our "${meeting.summary}" meeting has been moved to Thursday at 12pm.`,
    },
  });
}

​
What’s happening under the hood:

  • findFirstConnection retrieves the user’s connected Google Calendar and Slack accounts — no OAuth flows to build
  • apps.google_calendar(...) binds your connect once, so every subsequent call uses those credentials
  • search, write, and read map to the type of action: find data, create/update data, or list data
  • The SDK handles token refresh, retries, and API differences across apps — your agent just calls actions

​
Feedback

We want your feedback. The SDK is still taking shape and your input drives what we build next. Hit a bug? Missing a feature? Have an idea? Tell us about it