Trello · Gmail
Email new Trello cards with Gmail
Send an email when a new card is created on a selected Trello board. The message includes the card name, board, list, creation time and direct card link, so reviewers can follow project activity from their inbox. Connect Trello and Gmail, browse to the board to watch and enter a fixed recipient address. The email is sent from your connected Gmail account and appears in Sent. Includes its own fictional Stuttgart review example with German Unicode. Wait for the trigger to show Connected before creating the first card; initial webhook registration can take up to 15 minutes. Only new card creation after activation is processed: existing cards, copies, moves and later edits do not send an email. Card descriptions, attachments and members are not copied. The recipient can see the card title and board details; opening the card still requires Trello access. Messages use plain text, with no HTML, Cc or Bcc configured. Gmail sending limits apply. A manual rerun or a retry after an ambiguous provider failure can resend a message; this is a notification, not a two-way sync or an exactly-once delivery guarantee. Use your own address for the first test.
- 1. Trello · Create Card
- 2. Gmail · Email the card reviewer
View template →Use templateStripe · Trello
Create Trello review tasks for new Stripe refunds
Put new Stripe refunds in a Trello review queue. Choose a board and list with Browse; each refund.created event creates a card with Refund ID, individual refund amount in Stripe minor units, currency, status at creation, event time, live mode and Event ID, followed by four manual review prompts. Two partial refunds create separate tasks with their own amounts, not the payment's cumulative refunded total. Creation can be pending and does not confirm that the customer has received the money; check current status in Stripe. For currency minor units, 700 EUR means 7.00 EUR, while 700 JPY means 700 JPY. Includes its own fictional English Köln workshop example with German characters. Earlier refunds and later status changes are not imported or synchronized. Customer contacts, card details, refund reasons, instructions and metadata are excluded. Cards inherit board visibility. The workflow logs refunds without issuing refunds, contacting customers or closing cards automatically. Test in Stripe sandbox first. Manual reruns can duplicate tasks.
- 1. Stripe · Refund Created
- 2. Trello · Create the refund review task
View template →Use templateStripe · Trello
Create Trello offboarding tasks for canceled Stripe subscriptions
Queue a Trello offboarding review when a Stripe subscription actually ends. Select a board and list with Browse; each customer.subscription.deleted event creates a card containing Subscription ID, final status, currency, event Unix seconds, live mode and Event ID, plus four review prompts. Scheduling cancel_at_period_end only emits an update and does not create a card until termination. Includes a fictional English Bremen studio ended-trial example with German characters. Ended trials and paid subscriptions are included without assuming voluntary churn or lost revenue. The event time is the termination notification, not the earlier cancellation request. Multiple prices are supported without inferring MRR from the first item. Review current Stripe details, outstanding invoices and your retention policy before changing access. Existing cancellations and later edits are not imported or synchronized; onboarding cards are not updated. Customer contacts, cancellation feedback/comments, private descriptions, payment details and metadata are excluded. Cards inherit board visibility. The template creates a review task; it does not cancel subscriptions, issue refunds, revoke access or contact customers. Test in Stripe sandbox first. Manual reruns can duplicate cards.
- 1. Stripe · Customer Subscription Deleted
- 2. Trello · Create the subscription offboarding task
View template →Use templateStripe · Trello
Create Trello review cards for successful Stripe payments
Give successful Stripe payments a place in your Trello review queue. Choose a board and list with Browse; each new payment_intent.succeeded event creates a card with PaymentIntent ID, Amount received (Stripe minor units), Currency, Event created (Unix seconds), Live mode and Event ID, followed by four manual review prompts. Includes payments without an invoice and its own fictional English Dresden workshop example with German characters. Uses amount_received rather than the requested amount: 4900 EUR minor units means 49.00 EUR, while 4900 JPY means 4900 JPY. Failed, pending and canceled payments do not create cards. Check Stripe and delivery requirements before approving fulfillment; payment success does not confirm settlement in your bank. Existing payments and later refunds, disputes and payouts are not imported or synchronized. Customer contacts, card details, client secrets and metadata are excluded. Cards inherit board visibility, so select a board appropriate for payment records. This workflow does not charge customers, issue refunds, fulfill orders or send messages. Test with a fictional Stripe sandbox payment first; Live mode false identifies test data. Manual reruns can duplicate cards.
- 1. Stripe · Payment Intent Succeeded
- 2. Trello · Create the successful payment review task
View template →Use templateTrello · Google Calendar
Schedule next-day reviews for new Trello cards
Reserve a 30-minute review in Google Calendar when a new Trello card is created. Connect Trello and Google Calendar, browse to the source board and destination calendar, then keep the prepared date mappings. Two Formatter steps set the review to exactly 24 hours after the Trello creation timestamp and its end 30 minutes later. Adjust the +1 day and +30 minutes expressions if your team needs a different interval. Each event uses the card name in its title and includes the card ID and a Trello link. Includes its own fictional English Hannover planning example with German characters. Publish and wait for the Trello webhook to show Instant before creating cards; registration can take up to 15 minutes. This listens for createCard only: existing cards, copies, moves, later edits and due-date changes are not synchronized. The schedule uses creation time, not the card due date, business hours or working days. UTC calculations preserve the instant; Google Calendar displays it in your calendar timezone, and daylight-saving changes can shift the local clock time. No availability check is performed, so reviews may overlap. Descriptions, comments, attachments and member details are not copied. No attendees or invitation emails are added; the selected calendar's normal visibility and reminders apply, and the Trello link still requires board access. Test on a dedicated calendar first. Manual reruns can create duplicate events.
- 1. Trello · Create Card
- 2. Formatter · Set review to 24 hours after creation
- 3. Formatter · End review 30 minutes later
- 4. Google Calendar · Create the card review event
View template →Use templateStripe · Trello
Create Trello onboarding tasks for new Stripe subscriptions
Start a manual onboarding queue when a Stripe subscription is created. Connect Stripe and Trello, then browse to your board and list. Each card records Subscription ID, status at creation, currency, event Unix seconds, live mode and Event ID, followed by a short onboarding review checklist. Listens only for customer.subscription.created and includes its own fictional English Stuttgart studio trial example. Trials and incomplete subscriptions also create cards: subscription creation is not proof of payment or permission to grant access. Verify current subscription status and your onboarding policy in Stripe before provisioning anything. A subscription may contain multiple prices; this task does not infer a total, paid revenue or MRR from the first item. Existing subscriptions, renewals, status changes and cancellations are not imported or synchronized. No customer contacts, payment details or metadata are copied. Cards inherit board visibility. The workflow does not create subscriptions, charge customers, grant access or send messages. Test in Stripe sandbox first; Live mode false identifies test events. Manual reruns can duplicate cards.
- 1. Stripe · Customer Subscription Created
- 2. Trello · Create the subscription onboarding task
View template →Use templateStripe · Trello
Create Trello cards for paid Stripe invoices
Turn newly paid Stripe invoices into Trello review tasks. Connect Stripe and Trello, then browse to your board and list. Each card records Invoice ID, amount paid in original Stripe minor units, currency, event Unix time, live-mode flag and Event ID, plus a short handoff checklist. Listens only for invoice.paid and includes an independent fictional English Hamburg invoice example. Paid invoices can include zero-value invoices, customer balance or payments recorded outside Stripe; a card is not proof of a new card charge, payout or an order ready to ship. Verify the invoice and delivery requirements in Stripe before fulfilling anything. Amounts are not converted: 1900 EUR means 19.00 EUR, while 1900 JPY means 1900 JPY. Only future events create cards. Existing invoices, edits, refunds and disputes are not imported or synchronized, and recurring paid invoices can create separate tasks. No customer contacts, addresses, payment details, invoice PDFs, hosted links or metadata are copied. Cards inherit board visibility. The workflow does not charge customers, send messages, ship orders or issue refunds. Test in Stripe sandbox first; Live mode false identifies test events. Manual reruns can duplicate cards.
- 1. Stripe · Invoice Paid
- 2. Trello · Create the paid invoice review task
View template →Use templateStripe · Trello
Create Trello follow-up cards for failed Stripe payments
Create a Trello follow-up card when a Stripe PaymentIntent payment attempt fails. Connect Stripe and Trello, then browse to a board and list for payment review. The card contains the PaymentIntent ID, attempted amount in original Stripe minor units, currency, event creation time in Unix seconds, event ID and live-mode flag, followed by a short review checklist. Assign an owner in Trello and check the latest payment status in Stripe before contacting anyone: a later retry may already have succeeded. Each new failed-attempt event creates a separate card, even for the same PaymentIntent. Existing failures are not imported, and later success does not update or close the card. Amounts are not converted: 2900 EUR means 29.00 EUR, while 2900 JPY means 2900 JPY. This does not retry charges, issue refunds, send customer messages or implement invoice retry schedules. No customer contact details, card data, client secrets, raw error messages or metadata are copied. Cards inherit board visibility. Includes a fictional English Nürnberg workshop example. Test in Stripe sandbox first; Live mode false identifies sandbox events. Manual reruns can create duplicate cards.
- 1. Stripe · Payment Intent Payment Failed
- 2. Trello · Create the payment review card
View template →Use templateSlack · Trello
Create Trello cards from Slack task messages
Turn Slack messages containing [Task] into Trello cards. Connect Slack and Trello, choose the Slack channel to watch, then browse to the destination board and list. The keyword [Task] is prefilled and matched anywhere in the message, without case sensitivity. Bot messages are ignored. Matching human thread replies also create cards; edits and deletions do not. Each card uses the message text as its title and includes the source channel link, author ID and message timestamp. Keep task messages short and use plain text: Slack mentions and formatting are copied as supplied rather than converted. Includes its own fictional English task example with German characters. Add FastHook to the source channel before activating. Leaving Channels empty watches every channel accessible to the connection. Only new events after activation are processed; existing messages are not imported. This is one-way task capture, not status synchronization. Files and thread history are not copied. Message text becomes visible to members of the destination Trello board. Manual reruns can create duplicate cards.
- 1. Slack · New Keyword Mention
- 2. Trello · Capture the Slack task
View template →Use templateGitHub · Trello
Create Trello follow-up cards for published GitHub releases
Turn published GitHub releases into Trello cards for release checks and follow-up tasks. Connect the FastHook GitHub App and Trello, browse to the repository to track, then select a destination board and list. Each card includes the release tag, optional title, repository, author, pre-release flag, publication time and GitHub link. The Actions filter is prefilled with published. Both stable releases and published pre-releases are included. Draft releases, edits and deleted releases do not create cards. Includes an independent fictional English release example. Release notes, assets and source code are not copied. Only new publication events after activation are processed; existing releases are not imported. This creates a tracking card; it does not deploy code, verify deployment or synchronize later changes. Card details become visible to members of the destination board. Manual workflow reruns or unpublishing and republishing a release can create duplicate cards.
- 1. GitHub · Release
- 2. Trello · Create release follow-up card
View template →Use templateGitHub · Trello
Create Trello review cards from new GitHub pull requests
Turn newly opened GitHub pull requests into Trello cards for your review queue. Each card includes the PR title, number, repository, author, source and target branches, draft flag, creation time and GitHub link. Connect the FastHook GitHub App and Trello, browse to the repository to track, then choose a destination board and list. The Actions filter is prefilled with opened. Draft pull requests are included, with their draft flag shown in the description. Edits, new commits, reviews, closed and reopened PRs do not create another card. Includes an independent fictional English review example. Only new webhook events after activation are processed; existing PRs are not imported. This is one-way card creation, not review assignment or status synchronization. PR bodies, code changes and attachments are not copied. Card details become visible to members of the destination board. Manual workflow reruns can create duplicate cards.
- 1. GitHub · Pull Request
- 2. Trello · Create pull request review card
View template →Use templateHubSpot · Trello
Create Trello follow-up cards for new HubSpot contacts
Create a Trello follow-up card whenever a new contact is created in HubSpot. Connect HubSpot and Trello, then browse to a board and list. Each card contains the contact ID, a direct HubSpot record link and an editable follow-up plan. Only contact.creation events received after activation create cards; existing contacts, later edits, merges and deletions are not imported or synchronized. HubSpot creation webhooks provide record IDs, not contact names or email addresses, so these profile fields are not copied. Opening the record link requires existing HubSpot access. Includes its own fictional contact-created example. Choose a board appropriate for CRM follow-up and test with one fictional contact first. This workflow does not contact the person, assign an owner automatically, or change CRM permissions.
- 1. HubSpot · Contact Creation
- 2. Trello · Create a CRM follow-up card
View template →Use templateStripe · Trello
Create Trello onboarding cards for new Stripe customers
Start a customer onboarding card in Trello when a new customer is created in Stripe. Each card includes the customer name, email, customer ID, event ID and live-mode flag. Connect Stripe and Trello, then browse to the destination board and list. Includes a fictional English sandbox example with German characters. Only customer.created events received after activation are processed; existing customers and later edits are not imported or synchronized. A new customer record does not mean a payment or subscription exists. Customer ID remains in the card title even if the name is blank, and name or email may be empty. No payment details, addresses, tax IDs or metadata are copied. Choose a private board appropriate for customer contact information. Test with a fictional Stripe sandbox customer first; Live mode false identifies sandbox events.
- 1. Stripe · Customer Created
- 2. Trello · Create a customer onboarding card
View template →Use templateTrello · Notion
Create Notion project pages for new Trello cards
Start a project brief in Notion whenever a new card is created on your Trello board. The new page uses the card title and includes Overview, Tasks and Notes headings ready for your team to fill in. Connect Trello and Notion, select a board, and browse to the parent Notion page that the integration can access. Publish and wait for the Trello webhook to connect before creating a card; registration can take up to 15 minutes. Includes a fictional English project example with German characters. Only new card creation after activation is processed; existing cards, copies, moves and later edits are not synchronized. Card descriptions, comments and attachments are not copied. Each distinct new card creates a separate page, even when titles match. Page access follows the selected parent in Notion. This creates child pages, not database rows.
- 1. Trello · Create Card
- 2. Notion · Create a Notion project brief
View template →Use templateTrello · Slack
Send new Trello cards to a Slack channel
Keep your project channel informed when a new card is created on a selected Trello board. Each Slack message contains the card name, board, list and a direct card link. Connect Trello and Slack, choose the board to watch and a channel where the FastHook bot can post. Includes its own fictional English project handoff example. Messages use plain text with link previews disabled; descriptions and attachments are not copied. Wait for the trigger to show Connected before creating the first card; initial webhook registration can take up to 15 minutes. Only new card creation after activation is processed. Existing cards, copied cards, moves and later edits do not send another message. This is a one-way notification, not a status sync. Card names and board details become visible to everyone in the destination channel; the card link still requires Trello access.
- 1. Trello · Create Card
- 2. Slack · Notify the project channel
View template →Use templateGitHub · Trello
Create Trello cards from new GitHub issues
Turn newly opened GitHub issues into Trello cards for your triage queue. Each card includes the issue title, number, repository, author and a link back to GitHub. Connect the FastHook GitHub App and Trello, select the repository you want to track, then choose a destination board and list. The Actions filter is prefilled with opened: edits, comments, closed and reopened issues do not create cards. Includes a fictional English issue example. Only new webhook events received after activation are processed; existing issues are not imported. This is one-way card creation, not status synchronization. Issue bodies and attachments are not copied. Issue titles and repository details become visible to members of the destination board.
- 1. GitHub · Issues
- 2. Trello · Create issue triage card
View template →Use templateTrello · Google Drive
Create Google Drive project folders for new Trello cards
Prepare a project workspace in Google Drive whenever a new card is created on your Trello board. The folder takes the card name and is created inside the parent folder you choose. Connect Trello and Google Drive, select a board and optionally a writable destination folder, then publish. With no parent folder selected, folders are created in My Drive. Includes its own fictional English project example. Wait for the Trello trigger to show Connected before creating a card; initial webhook registration can take up to 15 minutes. Only new card creation after activation is processed. Existing cards, copies and later renames are not synchronized. Each distinct card creates a separate folder, even when card names match. This template creates an empty folder and does not copy files, add card attachments or change sharing permissions. Folder access follows its destination in Drive.
- 1. Trello · Create Card
- 2. Google Drive · Create project folder
View template →Use templateGoogle Drive · Trello
Create Trello review cards for new Google Drive files
Build a document review queue in Trello when new files are created in Google Drive. Each card uses the file name and includes a direct Drive link plus review instructions. Connect Google Drive and Trello, choose the folder to watch, then select a board and list. Leaving the folder empty watches the connected Drive. Includes a separate fictional English design-brief example. Only direct children of the selected folder are watched. Detection uses creation time: moving older files into the folder is not guaranteed to create a card. Polling can include files from roughly the minute before setup; older files and later edits are not synchronized. Cards have no automatic assignee or due date. The Drive link does not grant access; reviewers need existing file permissions.
- 1. Google Drive · New Files
- 2. Trello · Create document review card
View template →Use templateGoogle Calendar · Trello
Create Trello preparation cards for new Google Calendar events
Turn newly scheduled Google Calendar events into Trello preparation cards. Each card contains the event title and a direct link to its current schedule and details. Connect Google Calendar and Trello, choose a calendar, then select the destination board and list. The primary calendar is preselected. Includes its own English workshop example and supports timed and all-day events. The first poll establishes a baseline; only events created afterwards are processed. Existing events and later edits are not synchronized. Cards have no automatic due date, attendees or assignees. Use the event link for the authoritative meeting time.
- 1. Google Calendar · New Event
- 2. Trello · Create meeting preparation card
View template →Use templateTrello · Google Sheets
Log new Trello cards in Google Sheets
Keep a searchable spreadsheet log of new Trello cards. Each new card adds one row with Card ID, Card name, Board, List, Created at and Card URL. Connect Trello and Google Sheets, choose a board, and select a worksheet with these six headers in columns A-F. Mappings are already prepared; adjust them if your headers differ. Values are written as plain text. Includes its own English example card. Tracks new card creation after activation, not existing cards, copied cards or later updates. Initial webhook registration can take up to 15 minutes. Confirm the trigger is connected before creating your first card.
- 1. Trello · Create Card
- 2. Google Sheets · Log new card
View template →Use templateTrello · Telegram Bot
Send Telegram alerts for new Trello cards
Notify your team in Telegram whenever a new card is created on a selected Trello board. Each message includes the card name, board, list and a direct card link. Connect Trello and Telegram, choose the board and enter the destination chat ID. Messages use plain text. Includes its own English sample card. Watches new card creation after activation; existing cards, copies and later card updates are not imported. Your connected Telegram bot needs permission to send messages to the destination chat. Initial webhook registration can take up to 15 minutes; wait for the trigger to show Connected before creating the first card.
- 1. Trello · Create Card
- 2. Telegram Bot · Notify about new card
View template →Use templateGmail · Trello
Create Trello tasks from matching Gmail emails
Turn new inbox emails matching your Gmail search into Trello tasks. The email subject becomes the card title; sender, date, message body and a Gmail link are included in its description. Connect Gmail and Trello, review the prefilled Gmail search subject:"[Task]", then choose a Trello board and list. Includes an English example request. Processes newly received matching inbox messages, not historical mail or later label changes. Email content is copied to the selected board: use a private test list first.
- 1. Gmail · New Email Matching Search
- 2. Trello · Create email task
View template →Use templateGoogle Sheets · Trello · Telegram Bot
Turn Google Sheets leads into Trello cards and Telegram alerts
Turn each new Google Sheets row into a Trello card with the lead name, email, company and request, then send the card link to Telegram. Use the column headers Name, Email, Company and Request, or adjust the mappings. Connect your accounts, choose a spreadsheet and worksheet, select a Trello board and list, and enter your Telegram chat ID. Includes an English example lead. New rows added after activation are processed; existing rows are not imported.
- 1. Google Sheets · New Row Added
- 2. Trello · Create lead card
- 3. Telegram Bot · Send lead notification
View template →Use template
