Select platforms to listen for activities from it (e.g GitHub, Stack Overflow, etc)

If activity content contains any of these keywords, automation will be triggered.

Include activities from team members or not

Unique identifier of a member (e.g returned by a new member or a new activity trigger)

The ID of the note you want to search for

The unique Id of the activity in the platform (e.g. the id of the message in Discord). If Id doesn't exist on the provided platform, a new activity is created. Otherwise, the existing activity is updated (upsert). If you don't have an Id for activity, you can create a random one using Zapier.

The ID of the member who performed the activity

Type of activity. You can see existing activity types [here](https://docs.crowd.dev/docs/activity-types-and-scores) (use value field). Also, you can use here any custom activity type you like. Activity types should be unique for each platform.

Note: custom activity types shouldn't contain spaces and underscores.

Platform on which the activity took place. You can use any custom platform name here (e.g Luma, Facebook, DevRel Meetup, etc). You shouldn't use here platforms natively supported by crowd.dev (e.g GitHub, Discord, etc)

Date and time when the activity took place

Body of the activity. Any text that describes activity (e.g message, feedback from a webinar, etc)

Channel of the activity (e.g name of the channel on Slack, name of the repo on GitHub, etc). You can use here basically anything, it is just an additional way to distinguish between different activities happening on one platform.

The id of the parent activity in the platform (e.g. the id of the parent message in Discord), if the activity has a parent. This field can be used to link related activities together, in the app these activities will be shown as a conversation. To use this field, you should first create the parent activity.

Username of the member in the specified platform.

Email address of the member. Should be a valid email if present.

Bio of the member (showed in crowd.dev member profile)

Avatar URL for the member. It should point to a png picture. It will be shown as a member's profile picture in crowd.dev.

URL of the member profile on the specified platform.

Reach of the member. It can be a number of followers / subscribers of the member on the specified platform (e.g number of Twitter followers).

Type of activity. You can see existing activity types [here](https://docs.crowd.dev/docs/activity-types-and-scores). (use value field). Also, you can use here any custom activity type you like. Activity types should be unique for each platform.

Note: custom activity types shouldn't contain spaces and underscores.

The body of the note. Simple HTML is allowed here.

Member IDs of members associated with this note

The emails for contacting the organization.

The phone numbers for contacting for the organization.

The URL of the parent organization if it has one (for example if it has been acquired).

The number of employees of the organization.

Members associated with the organization. Each element in the array is the ID of the member.

Usernames of the member in each platform. Exactly one for each platform in which the member is active.
Example: { github: 'iamgilfoyle', discord: 'gilfoyle '}

Platform for which to check member existence (based on username).

Bio of the member (shown in crowd.dev member profile)

URL of the member profile on the specified platform (e.g link to a Twitter page of the user).

Tasks associated with the member. Each element in the array is the ID of the task.

Tags associated with the member. Each element in the array is the ID of the tag.

Notes associated with the member. Each element in the array is the ID of the note.

Activities associated with the member. Each element in the array is the ID of the activity.

Users assigned with the task. Each element in the array is the ID of the user.

Members associated with the task. Each element in the array is the ID of the member.

The ID of the organization. It is returned by Create Organization action, or you can find it in the end of /organizations URL in crowd.dev.

Usernames of the member in each platform. Exactly one for each platform in which the member is active.

Platform for which to check member existence.

Member IDs of the members associated with this note

crowd.dev is an open-source suite of community and data tools built to unlock community-led growth for your organization.

crowd.dev

Instantly build dynamic interfaces that connect to Zaps and a data source (like Tables). Interfaces gives you a drag-and-drop way to build visual workflows for any business process, without writing code.

Zapier Automation Platform

PRODUCTS

CAPABILITIES

Solutions

By team

By app

By use case

Zapier for

By team

Learn more

Get help

Developer resources

crowd.dev Integrations

crowd.dev Help & Support

About crowd.dev

Related categories

Similar apps

Zapier Interfaces