Skip to content

Form Submissions

Form Submissions becomes important when your agent uses Request Form to collect structured information.

If your agent does not use forms yet, this page may stay empty. That is normal.

Submitted consultation forms with filters and structured response fields

What this page is for

Use this page when the conversation hands off from free-form chat into structured intake.

For Consultation Desk, that usually means things like:

  • callback contact details
  • preferred follow-up windows
  • intake information that should not be reassembled from chat manually

How operators use it

Once submissions start arriving, this page becomes an operational queue:

  • review what the user submitted
  • confirm whether the information is complete
  • hand it to the right human workflow

Review notification behavior

The read-only notification summary follows the current filters. With All forms selected, it shows the workspace rule status and destinations plus the number of forms with individual settings. With a specific form selected, it shows whether the form uses the workspace default, custom destinations, or notifications off, together with the destinations that will actually receive the notification. Select Manage workspace notifications to open the Form submitted event in Workspace Notifications.

The rule editor there can only select existing, compatible destinations from the workspace catalog. The Form Submissions page does not provide notification destination controls.

To add, edit, test, verify, enable, disable, or delete a destination, use the Destinations tab in Workspace Notifications.

Form submission rules support these destination types:

  • Slack incoming webhook sends a formatted submission message to a Slack channel.
  • Slack workflow webhook sends fields as a key-value payload for a Slack Workflow.
  • Email sends a submission notification to a verified email address.

For an email destination, send the verification email from Destinations and open its link before relying on delivery. Changing the email address requires verification again. Use a test notification after setup to confirm that the destination works.

Clearing a destination in a form notification rule stops that rule from routing to it after you save. It does not delete a shared destination that may be used by another rule.

Slack Workflow payload keys

Each form field becomes a top-level payload key:

  • The field label is used as the key. If the label is empty, the field name is used.
  • If multiple fields produce the same key, the latest value overwrites earlier values.
  • Codeer also includes event_type, form_name, form_request_id, submitted_at, submitted_by_external_user_id, workspace_name, workspace_id, agent_name, and agent_id.

Set stable, unique field labels in Agent settings → Tools → Request Form → Open Form Builder before connecting a Workflow.

Identity masking does not rewrite notification payloads

Form Submission notifications send submitted form fields to an external destination and may include the raw submitted_by_external_user_id. Mask end-user identity protects workspace UI responses; it does not replace identity values in notification payloads. Use only destinations that are authorized to receive this end-user data.

Keep webhook URLs private

Slack webhook URLs are secrets. Do not paste them into public documents, issue comments, screenshots, or source code.

When the page is empty

An empty page usually means one of three things:

  • the agent does not use Request Form
  • the form exists, but no one has triggered it yet
  • your rollout is still too early to generate submissions