Default channels apps

Default channel apps let you send emails, SMS messages, printed documents, and Berichtenbox messages, or add and delete archived documents from a flow. Active channels are available on the Apps overview page and in the flow designer.

Use a channel action to send or store a communication. Use its status object to handle a later event, such as an SMS delivery or a rejected print job.

Before you start

You need access to the project and its flow creation and editing actions. Channel configuration access is separate from flow access. See Roles and restrictions.

The channel must be active for your organization, with a configuration available for the action. For setup and configuration changes, see Default channels. For Email, check that the sending domain is ready to use; see Email.

Add or rearrange objects in a DRAFT flow. To change the structure of a published flow, create a new version. See Flows.

Add a channel action

1. Open your project, select Flows, and open a draft flow.
2. In the flow palette, open Apps and find Default Channels. Use Search... to find the channel if needed.
3. Drag the channel onto the canvas and open the object to configure it.
4. If Action type appears, choose the action under Choose the action this app should take.
5. Complete the channel settings described below. Use fixed values or select flow variables with the @ button where available. For fields with Select and Input modes, use Select for a listed option or Input for a value or variable.
6. Connect the action to the preceding and following objects, then save the flow.

For the complete save, test, and publication workflow, see Create a flow.

Configure Email

Open the Email action and complete these sections:

Section	What to configure
Settings	Choose a Domain. In Input mode, supply the domain configuration value, such as a domain selected for each data record.
From	Enter the sender's Name and Email address. The default domain fills the email address and makes it read-only. Selecting another domain makes the address editable.
Recipients	Enter To (Name) and To (Email address). Use Add recipient, Add CC, or Add BCC for additional recipients.
Content	Enter Subject and provide HTML content, plain text content, or both through the content selectors. At least one body must contain content.
Attachments	Add an Attachment name and Attachment path for each file you want to include. Use the file selector for the path where available.

Recipient email addresses must be valid. If sending fails with Either HTML or text content is required, check that the selected content resolves to a non-empty body for the data record.

For Mailgun configurations, Advanced also provides Tags. Separate tags with commas, using up to 10 tags and 128 characters in total.

For example, map To (Email address) to the recipient email in your interface data, enter a subject, and select the email content. To react to a later failure or interaction, add Email Status as described under Handle channel events.

For missing, rejected, or duplicate messages, see Email delivery troubleshooting.

Configure SMS

Open the SMS action. Under Delivery details, complete:

• From: A sender name of up to 11 characters, or a phone number with a country code of up to 14 digits. Sender names accept letters, numbers, and periods; do not include spaces or other symbols.
• To: The recipient's mobile number, including its country code. Use digits without spaces or symbols, for example 31612345678.

Under Content, select the plain text message. From, To, and the message content are required. The action uses the organization's SMS configuration; it does not show a configuration selector.

Use SMS Status to handle DELIVERED: SMS delivered or FAILED: SMS could not be delivered events.

Configure Print

Open the Print action and choose a Configuration for the printer setup. Complete the following fields:

Field	What to enter or select
File name	A name for the print file. Required.
Source	The PDF to print. Required. You can supply a project file path, an HTTP or HTTPS URL, or Base64-encoded PDF data.
Source system	The source system for the print job. Required.
Paper	The paper value for your print setup. Required.
Envelope	The AddComm article code for the envelope. Required.
Envelope type	Select the sheet range: 1 - 7 Sheets, 8 - 44 Sheets, 45 - 75 Sheets, 76 - 250 Sheets, or 251+ Sheets. Required.
Black & white	Choose Yes or No. In Input mode, use true or false.
Print method	Choose Simplex or Duplex. In Input mode, use S or D. Required.
Shipping method	Select the shipping option for the job. Registered sending requires an API connection with POSTNL. Required.
Postal date	Optionally enter a date in YYYY-MM-DD format. If left blank, today's date is used.
Postal code	Enter the postal code shown in the address on the PDF. Required.
Postal region	Choose Netherlands or Outside Netherlands. In Input mode, use NL or BU. Required.

In Input mode, the envelope type values are C5, C4, HAND_C4, HAND_MZ, and HAND_DS, in the order shown above. Shipping method values are BASIC, 24, AANGETEKEND, and PRIORITY for domestic standard shipping, 24-hour shipping, registered sending, and shipping outside the Netherlands, respectively.

If File source has an invalid file path appears, check that Source points to an existing project file or supply a valid URL or PDF value. Invalid print methods, postal regions, and postal dates also block the request.

Use Print Status to handle production updates. DELIVERED: File was delivered is a file-processing event; use the later print and send events to follow the job's progress.

Configure Berichtenbox

Open the Berichtenbox action and select OIN. Then complete:

Field	What to provide
Message type	The message type for the communication. Required.
BSN	The recipient's BSN. Required. For a production OIN, use the input field. The default sandbox configuration also offers selectable test outcomes.
Reference	Your reference for the message. Required.
Publication date	A valid future date and time in YYYY-MM-DD HH:mm:ss format. Required.
Subject	The message subject. Required.
Message	The message content selected through the text content selector. Required.
Attachment name and Attachment path	An optional PDF attachment. The form provides one attachment entry.

An empty, invalid, or past publication date produces Parameter Publication date is required, it needs to be valid and in the future. Use Berichtenbox Status to handle the later processing result, including recipients who are not active or subscribed.

Configure Archive

Add Archive to the flow and use Action type to choose whether to add or delete a document.

Add a document

1. Select the add-document action.
2. Under General information, choose Archive ID and a municipality under Municipalities. The listed municipalities depend on the selected archive. In Input mode, provide its municipality code.
3. Complete the fields for the selected archive:
   • The default sandbox configuration shows Document details and Dates. Set Intern document to Yes or No, and enter any relevant description, recipient, document type, subject number, and dates. Date placeholders use YYYY-MM-DD.
   • Other configurations show Document Metadata with the fields defined for that archive. Complete the required fields shown there.
4. Under Document, supply Document path. Use the file selector where available.
5. Connect and save the action.

The request requires a configured municipality and a document. Missing values can produce Parameter Municipality Code is required, Parameter Municipality Name is required, or Parameter Document is required. Check the selected archive and municipality if these errors appear.

Delete a document

1. Select the delete-document action and choose Archive ID.
2. Under Delete by, select one method:
   • Filters: Fill in at least one filter for the selected archive. The default configuration offers Recipient, Subject, Description, Processed on, Created on, and Published on. Other configurations offer filters based on their metadata fields.
   • File ID: Enter the id returned by the action that added the file to the archive. Use the variable picker to select the correct action result.
3. Connect and save the action.

Filters is selected by default. A filter-based request without a value is rejected. File ID requires a non-empty ID. For default archive date filters, use YYYY-MM-DD or an ISO 8601 timestamp, such as 2026-10-22T10:00:00Z.

Use action responses

Channel actions expose these response fields for later steps:

Field	Use
id	Flowize's identifier for the request. Use the appropriate action's ID in the channel status object's Webhook ID value. For Archive deletion by File ID, use the add action's returned ID.
message	The message returned for the request.
status_code	The status code returned for the request.
errors and error_code	Error details when a request fails.
credits	Additional response field available for SMS.

Use the @ variable picker to select a result from the correct action, especially when a flow contains several actions for the same channel. A successful action response does not establish that a later delivery or processing event has occurred.

Handle channel events

1. In the flow palette, open Webhooks and find Default Channels Webhooks.
2. Drag the matching status object onto the canvas: Email Status, SMS Status, Print Status, Berichtenbox Status, or Archive Status.
3. Set Webhook ID value to the id returned by the channel action you want to monitor. For example, the Email status field shows @app.default_channel_email.send.id@ as an example. Select the actual variable for your action with @.
4. Under Events, select the event to handle.
5. Connect both outputs:
   • The bottom EVENT output leads to the steps for a matching ID and event.
   • The right output continues when no matching response is available at that point. This does not mean that delivery failed.
6. Save the flow and test the complete event-handling path.

The status object checks the request ID together with the selected event. For example, an Email Status object configured for FAILED: Email could not be delivered reacts to failure events for that email request, rather than every email failure in the project.

The listener options include Set as a Persistent listener? and Listen only to new webhook responses?. These affect later responses and repeated execution. Follow Webhooks in the Flows when designing the continuation path and listener lifetime.

Available events

Status object	Choices in Events
Email Status	CLICKED: Email link was clicked; FAILED: Email could not be delivered; OPENED: Email was opened; SPAM: Recipient clicked on SPAM.
SMS Status	DELIVERED: SMS delivered; FAILED: SMS could not be delivered.
Print Status	DELIVERED: File was delivered; READY: File is ready to process; REJECTED: File was rejected; MERGE: File has been merged; PRINT: File is printing; INSERT: File is being inserted; INSERT: File was inserted; SEND: File is being sent; SEND: File is sent; CANCELLED: File was cancelled.
Berichtenbox Status	PROCESSED: Message was sent; TECHNICAL_PROBLEM: A technical error occurred; PUBLICATION_DATE_TOO_FAR_IN_THE_FUTURE; NOT_ACTIVE_OR_SUBSCRIBED: Recipient is not active or subscribed; ATTACHMENT_TOO_LARGE: The attached file exceeds the allowed size; CREATION_DATE_TOO_FAR_IN_THE_PAST; MESSAGE_ALREADY_EXISTS: Duplicate message; MESSAGE_TYPE_NOT_SUPPORTED: Unsupported message format.
Archive Status	ADDED: File was archived; DELETED: File was removed from the archive.

Email does not offer a delivered event in this selector. For opens and clicks, check the domain's tracking settings.

Status responses expose id, event, event_timestamp, and data. Email also exposes email; SMS exposes phone_number and provider details under data. Use these results in subsequent steps when handling the event.

Test channel actions and events

Use Test an individual App to inspect action inputs and the incoming response. Channel action tests call the provider, so use the intended sandbox configuration or test destination. An individual action test does not register the listener needed for subsequent channel events. Status objects do not offer an individual Test button; verify their behavior through a data record running in the flow.

For missing channels, configuration errors, or event-handling issues, see Default channel troubleshooting.