Slack workflow forms: reconcile response exports

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Define the reconciliation key

Slack allows workflow managers on supported plans to download Workflow Builder form responses. When a workflow has several forms, the manager selects the relevant form before export. Developer-built workflows use different API or CLI paths. Record the workflow, form step and export time so that files from separate response sets are not combined without context.

Build a three-response fixture

Submit three fictional requests: one complete response, one optional-field omission and one corrected resubmission. Export the intended form and compare it with the downstream channel messages or records produced by the workflow.

Normalize time deliberately

Slack documents that the Z suffix on Submission Timezone timestamps in exported CSV files represents UTC. Preserve the raw value and create a separate localized interpretation when needed. Do not rewrite the original timestamp or infer submission order from filenames alone.

1. Name the workflow and exact form step.
2. Record export requester and UTC export time.
3. Validate headers before importing rows elsewhere.
4. Keep blank values distinct from missing columns.
5. Match each fixture to its downstream outcome.
6. Apply a written duplicate or correction policy.
7. Store or delete the export under the organization's retention rules.

Accept attributable responses

Accept the export when every test row maps to the intended form and outcome, timestamps retain their timezone meaning and corrections do not silently overwrite history. Deletion requests and access to exports remain subject to Slack's documented owner and administrator process.