Crowd.dev Trigger

Starts the workflow when Crowd.dev events occur.

Overview

The Crowd.dev Trigger node for n8n starts workflows when specific events occur in Crowd.dev, such as a new activity or a new member joining. It is designed to be used as a trigger node, meaning it initiates an automation based on real-time webhooks from Crowd.dev.

Common scenarios:

Automatically process or enrich data when a new activity (e.g., post, comment) happens in your Crowd.dev community.
Onboard or notify team members when a new member joins the community.
Integrate Crowd.dev events with other tools (e.g., send Slack notifications, update CRM records).

Practical example:
If you want to automatically add new Crowd.dev members to a mailing list, you can use this node to trigger the workflow whenever a "New Member" event occurs.

Properties

Name	Type	Meaning
Trigger	options	Specifies which Crowd.dev event will trigger the workflow. Options are: - New Activity: Triggers when a new activity occurs. - New Member: Triggers when a new member joins.

Output

The node outputs the JSON payload received from Crowd.dev via webhook. The structure of this output depends on the event type and the data sent by Crowd.dev, but it typically includes details about the activity or member that triggered the event.

Example output (structure may vary):

{
  "id": "event_id",
  "type": "new_activity",
  "data": {
    // Event-specific fields, e.g., activity details or member info
  },
  "timestamp": "2024-06-01T12:34:56Z"
}

The output is always in the json field.
No binary data is produced by this node.

Dependencies

External Service: Requires access to a Crowd.dev instance.
API Key: Needs valid Crowd.dev API credentials configured in n8n under the name crowdApi.
n8n Configuration: The node must be accessible via a public URL so Crowd.dev can send webhook requests.

Troubleshooting

Common issues:

Webhook not triggering: Ensure your n8n instance is publicly accessible and the webhook URL is correctly registered in Crowd.dev.
Authentication errors: Double-check that the crowdApi credentials are set up correctly in n8n.
Missing or invalid webhook ID: If the workflow is deleted or credentials change, re-create the webhook to refresh the registration.

Error messages:

401 Unauthorized: Indicates invalid or missing API credentials. Update your crowdApi credentials in n8n.
404 Not Found: The webhook might have been deleted or the ID is incorrect. Try re-creating the trigger node.
Connection timeout: Your n8n instance may not be reachable from Crowd.dev. Check network/firewall settings.