Send Message
This chapter was written from the product's source code and has not yet been checked by a person on a running Cogneris. If what you see on screen differs, the screen is right — please tell your Cogneris contact so the chapter can be corrected.
Send Message is no longer offered in the palette: the Workflow service has no step that runs it, and a workflow that contains it cannot be published. A draft that still has one opens with the notice This phase cannot run yet on the node and in its settings; remove the node before you publish. To deliver a result, use Send.
| Palette | Not offered (no longer) |
| Outputs | None is ever taken, because the phase never completes |
| Content status | From source; not observed (workflow-fe f88c5c1, workflow-be 6703373, 2026-10-22) |
When to use it
Not yet. The templates Business onboarding and Contract signature of Create Workflow used to end with it; they now end with a Send phase. A draft created from them before still has Send Message: replace it with Send (or remove it) before you publish.
What happens in a run
When a process reaches Send Message, the service finds no step for the phase type send_message. The step fails with the error No executor registered for phase 'send_message' and the whole run fails. Nothing is sent: no message, no e-mail and no webhook call.
Publishing does not warn you: the service accepts a workflow containing this phase. Unlike Send, it does not even check that the endpoint is HTTPS. The only thing publishing does for it is create a signing secret if an endpoint is set and none exists yet.
Channels, recipients and message templates
There are none. The panel has no channel (e-mail, SMS, WhatsApp), no recipient and no message text or placeholders. To notify a person through a channel, see the Signature phase, which has its own channel setting, or deliver to your system with Send and send the message from there.
Configuration
The panel is the same as the Send panel. The fields are stored with the phase but are not used, because the phase never runs. Its header shows the phase type as SEND_MESSAGE.
| Field | What it does | Required | Format / values | Default | Validation messages |
|---|---|---|---|---|---|
| Description | The name shown on the node | No | Text | Send Message | — |
| Subject | Stored; not used | No | Text | Empty | — |
| Integration name | Stored; not used | No | Text | Empty | — |
| Endpoint URL (HTTPS) | Stored; not used. Setting it creates a Signing secret, as on Send. | No | An https:// URL or a test URL | Empty | Enter a valid HTTPS URL. (in the panel only) |
| HTTP method | Stored; not used | No | POST, PUT, PATCH, DELETE | POST | — |
| Description (optional) | Stored; not used | No | Text | Empty | — |
| Signing secret | Shown to administrators only, while an endpoint is set. Not used. | — | 64 hexadecimal characters | Created with the endpoint, or at publish | — |
Buttons and actions
The panel shows the same buttons as Send — Test endpoint, Copy, Regenerate, Generate test URL, Use as endpoint, View requests and Revoke — and they behave as described in Send. Test endpoint really calls the endpoint. A test URL generated here receives nothing, because the phase never sends.
Common problems
| Message | Cause | What to do |
|---|---|---|
| The run fails at Send Message with No executor registered for phase 'send_message' | The service has no step for this phase | Replace the phase with Send, publish, and start the process again. |
| Enter a valid HTTPS URL. | The endpoint is not an absolute https:// address | Not relevant while the phase cannot run. |
| No requests received yet. Run the workflow to see deliveries here. in View requests | The phase never sends | Use a test URL on a Send phase. |
Related
- Send — the phase that delivers results
- Signature
- Design and publish a workflow
Last reviewed 2026-10-22 · Version 1.0.0 · Owner: product-documentation