Actions64
- Website Actions
- Conversation Actions
- People Actions
- Operator Actions
- Settings Actions
- Analytics Actions
- Availability Actions
- Campaign Actions
- Helpdesk Actions
- Visitors Actions
- Batch Actions
- Verify Actions
Campaign → Dispatch
AI-generatedOverview
This node operation dispatches a campaign in the Crisp platform. It is used to trigger the sending or activation of a specific campaign identified by its campaign ID for a given website. This is useful in marketing automation or customer engagement scenarios where campaigns need to be programmatically controlled and dispatched.
Use Case Examples
- Dispatch a promotional campaign to all subscribers of a website.
- Trigger a campaign dispatch after a specific event in a workflow, such as a user signup or purchase.
Properties
| Name | Meaning |
|---|---|
| Website ID | The website ID from your Crisp dashboard, identifying the website for which the campaign is dispatched. |
| Campaign ID | The ID of the campaign to be dispatched. |
| Additional Fields | Optional additional fields related to the campaign dispatch, such as email, first name, last name, phone, company, conversation state, block status, user assignment, role, domain, and verification string. |
Output
JSON
*- Response data from the Crisp API after dispatching the campaign
Dependencies
- Crisp API key credential for authentication
Troubleshooting
- Ensure the Website ID and Campaign ID are correct and exist in your Crisp dashboard.
- Verify that the API credentials are valid and have the necessary permissions to dispatch campaigns.
- Check network connectivity and Crisp API availability if requests fail.
- If the dispatch operation fails, the node may throw an error; enabling 'Continue On Fail' can help handle errors gracefully in workflows.
Links
- Crisp API - Dispatch Campaign - Official Crisp API documentation for dispatching campaigns.