Card creation via email Pro

Overview

Each eligible board can have its own inbound email address. When someone sends mail to that address, Saku creates a card on the board using the email contents.

• Subject becomes the card title.
• Message body becomes the card description.
• Attachments are imported onto the card.
• High-priority email headers can optionally set the card priority.

How to create cards via email

1. Open the target board.
2. Go to the board settings email intake area.
3. Turn on Enable card creation via email.
4. Copy the generated board address and send an email to it from an allowed sender.
5. Check the configured default list on the board for the new card.

If intake is turned off, the board keeps its settings but new emails will not create cards until the feature is re-enabled.

What happens after you send

When an email is accepted, Saku creates the card on the board and does not send a confirmation reply. Silence usually means success: open the board (or the recent inbound email log below) to see the new card.

If something goes wrong, such as the sender not being allowed, intake being disabled, or the message being too large, the sender receives an automatic error reply that explains the problem.

In practice: no reply within a few minutes means the card was created; an error reply means it was not.

Configure sender rules

You can decide whether the board accepts mail from everyone or only from approved senders.

• Allow all sender addresses is the simplest setup.
• Turn it off to enforce a sender whitelist.
• The whitelist can include individual email addresses or whole domains.
• Custom board email addresses require sender whitelisting to reduce abuse and spam.

Board address management

Each board has a unique address. You can copy it for day-to-day use or rotate it if it has been shared too widely.

• Copy address for teammates or tools that should send work into the board.
• Rotate address if the existing address should stop receiving new work.
• Custom address: set a memorable local part such as support or client-feedback if you want a cleaner address.

Card routing and defaults

Email-created cards still follow board rules. You can predefine how they should land:

• Default list: choose which list receives new email cards.
• Default priority: set the starting priority when the email itself does not provide one.
• Use email high-priority header: let the sender mark a message as urgent and map that onto the card priority.
• Labels to apply: automatically tag all cards created through this intake.

How inbound emails become cards

When an allowed email reaches the board address, Saku parses the message and creates a card using the subject and body. Files attached to the email are imported as card attachments. The card also records who sent the email so the origin is visible later on the board.

If you forward a message in (for example a customer email), Saku strips common reply prefixes from the title, removes the forward header block (From:, To:, and similar lines) above the quoted text, and keeps the rest of the body including signatures. Forwarded threads may get a short note at the top of the description suggesting a single-message forward for a cleaner card. Security rules still use the real sender of the email you send, not addresses parsed from the body.

Recent inbound email log

The email intake area shows a recent log so you can confirm what happened to each message.

• Created: a card was successfully created.
• Processing: the message is still being handled.
• Duplicate: the message was recognized as already processed.
• Failed entries include a reason so you can correct sender rules or configuration.

Troubleshooting

• No card created: confirm the board is on Pro or Max, intake is enabled, and the sender is allowed.
• Email rejected after setting a custom address: enable and maintain the sender whitelist.
• Card landed in the wrong column: update the default list in the intake settings.
• Priority did not change: verify whether the email included a high-priority header and whether that option is enabled.