Zapier Integration

Connect Zapier with crowd.dev to access 5,000+ apps

How to install

To start using the integration, go to the Integration settings and follow the steps to set up Zapier.

Supported triggers

Triggers are a Zapier way to listen for new events (basically webhooks). crowd.dev's Zapier integration supports two types of triggers: New Activity and New Member.

New Activity

This trigger is activated when a new activity happens in your community platforms connected to crowd.dev. For example, someone starred your repo, sent a message in Discord, etc.

You can make this trigger granular. For example, only activate it when someone opens a pull request on GitHub and mentions a specific keyword. On the other side of the spectrum, you can configure this trigger to be a "catch-all", but this setup is not recommended because it will be quite hard to distinguish between different events on a Zapier side. So the recommended configuration is to keep this trigger as narrow as possible.

New Member

This trigger is activated when a new member joins your community platforms connected to crowd.dev. In crowd.dev, a member is considered anyone who performed at least one action at your community platforms - e.g., joined a Discord server or did something on GitHub (the trigger is activated only once for each user).

This trigger can be configured as a "catch-all" (all new member activities for all active platforms) or only for specific platforms.

Supported Actions

Actions in Zapier are commands that the integration can perform (basically API calls). crowd.dev Zapier integration supports multiple actions:

Activity

  • Create or update activity for a member - takes a member object and information about activity and creates or updates an activity for this member in crowd.dev
  • Create or update activity - takes an activity object and creates or updates an activity in crowd.dev based on sourceId of activity and platform

It's worth noting, that these actions are intended only for activities from custom platforms not supported by crowd.dev. For example, they can be used to automatically creates activities for members who attended a meetup, purchased a swag, etc.

Members

  • Create or update member - takes a member object and creates or updates a member in crowd.dev
  • Update member - takes a member object and updates an existing member in crowd.dev based on memberId. Fails if the member doesn't exist.
  • Find task - returns a member object for an existing member based on memberId. Fails if the member doesn't exist.
  • Delete member - deletes an existing member based on memberId. Fails if the member doesn't exist.

Organization

  • Create organization - creates a new organization in crowd.dev
  • Update organization - updates an existing organization in crowd.dev by organizationId. Fails if the organization doesn't exist.
  • Find organization - returns a organization object for an existing organization based on organizationId. Fails if the organization doesn't exist.
  • Delete organization - deletes an existing organization based on organizationId. Fails if the organization doesn't exist.

Task

  • Create task - creates a new task in crowd.dev
  • Update task - updates an existing task in crowd.dev by taskId. Fails if the task doesn't exist.
  • Find task - returns a task object for an existing task based on taskId. Fails if the task doesn't exist.
  • Delete task - deletes an existing task based on taskId. Fails if the task doesn't exist.

Note

  • Create note - create a new note in crowd.dev
  • Update note - updates an existing note in crowd.dev by noteId. Fails if the note doesn't exist.
  • Find note - returns a note object for an existing note based on noteId. Fails if the note doesn't exist.
  • Delete note - deletes an existing note based on noteId. Fails if the note doesn't exist.