Skip to main content

Board Export+ Power-Up Guide

Board Export+ helps Trello users export board or card data into reusable files and scheduled deliveries. This guide explains the Power-Up screens, settings, and common workflows.

Quick Export Workflow

  1. Open Board Export+ from a Trello board or card.
  2. Use Start to confirm scope, file name, format, and export readiness.
  3. Use Fields to choose columns and their order.
  4. Use People and Labels when member or label data should be included or filtered.
  5. Use Presets to apply a saved or starter configuration.
  6. Use Preview to inspect the output shape.
  7. Click the main export button in the footer.

The sticky footer shows the board name, export readiness, selected card/list/field counts, format, and active filters.

Visual Walkthrough

Use these screenshots and the walkthrough GIF to understand the core Board Export+ flow before setting up your own exports.

Quick Video Guide

Board Export+ walkthrough

Product Screenshots

Export Setup

Board Export+ export setup

Choose the export scope, format, filters, and confirm readiness before downloading.

Field Selection

Choose Trello export fields

Select exactly which Trello fields appear in the export and control the column order.

Export Preview

Preview Trello export

Preview the export before downloading so reports are clean and client-ready.

Scheduled Exports

Schedule recurring Trello exports

Schedule recurring exports with timezone-aware run times, retained downloads, and delivery options.

Export History

Recent Trello export history

Access recent exports, copy client share links, and reuse previous settings.

Presets

Board Export+ presets

Apply starter presets or reuse saved configurations for consistent reporting.

Start

The Start tab is the main launch point for a one-time export.

  • Export check shows whether the current setup is ready, needs review, or is blocked.
  • Filename shows the generated file name before export.
  • Scope and filters control which cards are included.
  • Format controls the file type, such as CSV, XLSX, JSON, PDF, PNG, DOCX, or ZIP.

If export is blocked, follow the setup message first. Common blockers are no selected cards or no selected tabular columns for formats that require fields.

Fields

The Fields tab controls tabular columns and field order.

  • Enable fields such as board, list, card, description, labels, members, dates, custom fields, URLs, comments, activity, and attachments.
  • Reorder fields to control column order in CSV/XLSX/JSON-style exports.
  • Some fields depend on related options. For example, label output depends on label options, and member output depends on people options.

Use a smaller field set for client-ready exports and a broader field set for audits or backups.

People

The People tab controls member data.

  • People columns selects which people-related fields are included in the export.
  • Included people shows people currently in scope.
  • Removing a person from scope filters matching cards from the export run.

Blue “Included” states mean the option is selected for the export. Green is reserved for successful or verified states elsewhere.

Labels

The Labels tab controls label data.

  • Label output options controls whether label names, colors, and grouping flags are included.
  • Labels in scope shows labels currently available for this run.
  • Removing a label from scope filters matching cards from the export run.

Use label filtering when you only want to export cards tied to a client, status, department, or workflow label.

Presets

The Presets tab provides reusable export setups.

  • Starter presets apply common layouts for board snapshots, client reports, and detailed card exports.
  • Saved templates can be reused to keep team exports consistent.
  • Duplicating a preset is useful when you want a variant without changing the original setup.

Always review Start and Fields after applying a preset, especially when switching formats.

Schedule

The Schedule tab creates recurring exports using the current export setup.

Key schedule settings:

  • Name identifies the schedule in the history and management views.
  • Cadence controls daily or weekly recurrence.
  • Time and time zone control when the worker should run the schedule.
  • Delivery targets verify email recipients and webhook endpoints.
  • Delivery methods choose retained downloads, email delivery, webhook delivery, and public share options when available.

Schedules require the background worker to be running. If a schedule is due but nothing is delivered, check the worker process and environment variables.

Email Delivery

Email delivery sends scheduled export notifications to verified recipients. It is intended for real team or client recipients after an administrator has configured SMTP for the Board Export+ deployment.

Requirements:

  • SMTP is configured by the workspace/app administrator.
  • The recipient email address is verified from the Schedule tab.
  • The schedule is active and includes Email as a delivery method.
  • Download retention or public share links are enabled when recipients need a download URL in the notification.

User workflow:

  1. Add an email recipient in the Schedule tab.
  2. Open the verification email.
  3. Paste the token into the verification field.
  4. Select the verified recipient for delivery.
  5. Save the schedule.

Recipients receive an export-ready notification with schedule details, file metadata, and a download/share link when the schedule is configured to retain or share the generated file.

Webhook Delivery

Webhook delivery posts export metadata to a verified endpoint owned by your team, client, automation platform, or integration service. It is designed for production systems that want to react when a scheduled export finishes.

Requirements:

  • The receiver URL should use HTTPS in production.
  • The receiver must accept JSON POST requests.
  • The receiver must return a 2xx status for successful verification and delivery.
  • The receiver should store or process export.completed payloads using exportJobId as an idempotency key.
  • If the payload includes downloadUrl, the receiver can fetch the generated file while the retained artifact or public share link is still available.

Verification workflow:

  1. Paste the receiver URL into Verify webhook in the Schedule tab.
  2. Board Export+ sends a challenge request to the receiver.
  3. The receiver echoes the challenge token.
  4. After verification, select the endpoint under Webhook URL.
  5. Enable Webhook delivery and save the schedule.

During verification, Board Export+ sends:

{
"event": "board-export-plus.webhook_challenge",
"challenge": "..."
}

The endpoint must respond with the same challenge:

{
"challenge": "..."
}

When a scheduled export completes, Board Export+ posts:

{
"event": "export.completed",
"exportJobId": "...",
"scheduleId": "...",
"scheduleName": "...",
"format": "json",
"scope": "board",
"sourceId": "...",
"fileName": "...",
"completedAt": "...",
"downloadUrl": "..."
}

Treat webhook payloads as integration events. The receiving system should validate the event, handle duplicate exportJobId values safely, and return quickly with a success response.

History

The History tab shows recent export jobs when history saving is enabled.

  • Completed jobs can be downloaded while retained artifacts are available.
  • Failed jobs show status so you can adjust settings and rerun.
  • History depends on local/user settings and backend retention.

More And Advanced Settings

The More menu contains lower-frequency sections such as Schedule, History, Advanced, and Help & docs.

Advanced settings include request-level flags, branding defaults, and other controls that affect the current export request without changing Trello itself.

Power-Up Settings

Power-Up settings manage long-lived preferences.

  • Account & connection reconnects or disconnects Trello REST access.
  • Defaults control preferred format, filename pattern, and remembered setup behavior.
  • Dates & time zone controls how dates are interpreted and displayed.
  • History controls whether export history is saved and how long it remains visible.
  • Reset preferences clears saved preferences, branding, defaults, and remembered layouts.

Use settings when you want to change defaults for future exports. Use the export tabs when you want to change only the current run.

Export Formats

  • CSV/XLSX are best for spreadsheet workflows.
  • JSON is best for integration, automation, or backup-style output.
  • PDF/PNG/DOCX are best for presentation-style reports.
  • ZIP is best when exporting Trello attachment files and a manifest.

Not every option affects every format. For example, presentation branding matters most for report formats, while field order matters most for tabular formats.

Troubleshooting

Export Is Blocked

Check the Start tab export readiness message. Most blockers require selecting cards/lists or adding fields.

Schedule Did Not Run

Confirm:

  • The schedule is active.
  • nextRunAt is due.
  • The worker process is running.
  • Redis and Postgres are reachable.
  • Required worker environment variables are present.

Webhook Verified But No Delivery Appears

Verification is handled by the API. Actual scheduled delivery is handled by the worker. If verification succeeds but no export.completed event appears, check the worker.

Email Verification Does Not Arrive

Check spam folders, recipient spelling, token expiry, and SMTP settings. In local development, confirm MailDev is running and reachable.

Local Delivery Testing

For local development, MailDev can be used as a test inbox for email delivery.

Webhook delivery can be tested with a local receiver, webhook.site with a custom response, Pipedream, or another endpoint that can echo the verification challenge. Public webhook testing tools must be configured to return:

{
"challenge": "the incoming challenge value"
}

Privacy And Stored Data

Board Export+ may store Trello access tokens, export settings, schedules, template metadata, export job history, retained artifacts, and data included in generated exports. Treat exported files and public share links as sensitive if they include client, member, card, comment, or attachment information.