crowd.dev

Log a community activity in crowd.dev and simultaneously create or update the member record it belongs to — keeping engagement history and member profiles in sync in a single call.

Log a standalone community interaction event in crowd.dev without touching member data — useful when the member record already exists and you only need to append a new engagement signal.

Permanently delete a crowd.dev automation rule by ID — use this to programmatically retire stale triggers when a campaign ends or a data-source integration is removed.

Retrieve a specific crowd.dev automation rule by ID, returning its filter criteria, action type, and enabled status — useful for auditing or conditionally updating automation logic.

Return all crowd.dev automation rules configured in a workspace, letting the agent iterate over them to audit, report on, or selectively act on each rule.

Modify an existing crowd.dev automation rule's filters, actions, or enabled state — use when campaign targeting shifts or a channel URL changes without needing to recreate the rule from scratch.

Upsert a community member profile in crowd.dev by matched identity, merging new attributes like job title, organisation, or location without creating duplicate records.

Permanently remove a community member record from crowd.dev by ID — use for GDPR erasure requests or to clean up test profiles seeded during integration development.

Look up a specific community member in crowd.dev by email, GitHub handle, or platform identity — returning their full profile, engagement score, and linked identity attributes for decisioning.

Retrieve a filtered, paginated list of community members from crowd.dev — filtered by engagement score, tag, organisation, or last-active date — for bulk reporting or downstream processing.

Retrieve a paginated list of community activity events from crowd.dev filtered by type, member, source channel, or date range — used for reporting, trend analysis, and audit trails.

Retrieve a specific crowd.dev activity record by ID, returning its type, source, timestamp, and linked member — used to verify an event was captured or to retrieve metadata for downstream processing.

Patch specific fields on an existing crowd.dev member profile — such as adding a tag, updating their organisation, or changing their email — without replacing the full record.

Create a new crowd.dev automation rule from scratch — specifying its trigger type, filter criteria, and action — so agents can programmatically spin up engagement rules when a new campaign or integration launches.

Import or update a batch of community member records in crowd.dev in a single call — ideal for syncing large lists from conference exports, CRM data dumps, or partner integrations without hitting rate limits on individual upserts.

Fires when any new engagement event — a GitHub star, a Slack message, a forum post, or a custom activity — is ingested into crowd.dev, letting the agent react the moment a community signal appears.

Fires whenever a brand-new community member profile is created in crowd.dev — triggered by a first GitHub interaction, a Discord join, or any integration that introduces a previously unseen identity.

Fires whenever crowd.dev recalculates a community member's engagement score — useful for routing members to sales, triggering outreach, or flagging churn risk the moment the score crosses a threshold.

Fires when a crowd.dev internal automation rule executes — letting Actionist agents observe and respond to crowd.dev's own rule engine without polling, enabling cross-system orchestration on automation events.

Fires when any attribute on a crowd.dev member profile is updated — including custom fields like tags, engagement tier, or organisation — letting agents react to enrichment or manual edits in real time.

Fires the first time a crowd.dev member's organisation field is populated — either by enrichment or a direct update — enabling agents to route account-based signals to sales the moment a company affiliation is confirmed.