A configured workflow can send new note content to a selected Slack channel, or create a card on a Trello board. You record the note once, and the right place gets the content without anyone copying and pasting. The setup takes a few minutes, and it is worth testing on a throwaway channel or board first.
Tom runs a small repair shop. After each job he says a quick note into his phone: what he did, what parts he used, and whether the customer needs a call back. His business partner lives in Slack. Tom used to retype each note there. Now it arrives on its own.
Step 1: choose where the note should land
Pick one destination first. Two is fine later, but start with one.
Slack suits information people should see quickly: a recap, a heads-up, a handoff. A channel keeps it visible and searchable by the team.
Trello suits information that becomes work: a follow-up call, a part to order, a customer to chase. A card has an owner, a list, and a place in a process.
Ask yourself: do I want people to read this, or do I want someone to act on it? Read means Slack. Act means Trello.
Step 2: connect the destination
In LetsVoice, connectors are set up in your account, and they are available on plans that include them. For Slack, you authorise access and then choose the channel you want posts to go to. For Trello, you connect your account and pick the board and list where new cards should appear.
Use a test target for this step. Create a channel called something like "voice-test" or a board called "Test". If your first few attempts go wrong, nobody else sees the mess.
Step 3: build the workflow
A workflow needs a trigger and a step. For this job the trigger is "every new note." That means whenever you save a note, the workflow runs. The step is "send to Slack" or "create a Trello card."
Other trigger options are a mention word, where only notes containing a chosen word run the workflow, and a manual run, where you press a button on a specific note. These are the three choices. There is no clock-based trigger, so a workflow cannot run at a set time of day on its own.
For Tom, a mention word makes sense. He says "callback" at the end of any job that needs a follow-up, and only those notes become Trello cards. Everything else just goes to Slack.
Step 4: say exactly what gets sent
Be deliberate about the outbound action. In Slack, the workflow posts note content to the selected channel. In Trello, it creates a card with the note content on the board and list you picked. It does not move existing cards or edit ones that are already there.
Decide what the content should be. The transcript is usually too long for a channel. A summary, a title and a checklist read much better. Choose the output that someone glancing at their phone would actually read.
Step 5: test with one sample note
Record something short and boring. "Test note for the workflow. Replace the filter on the blue van. Call Dana tomorrow." Save it and watch the destination.
Check these things:
- Did it arrive in the right channel or list?
- Is the title readable?
- Did the checklist items come across as separate lines?
- Is anything cut off?
If something is wrong, change one thing and run again. Changing three things at once makes it hard to see what helped.
Step 6: go live gradually
Once the test looks right, point the workflow at the real channel or board. For the first week, look at every result. A voice note is spoken language, and a mistake in a name or a number will occasionally slip through. Anything important, like a part number or a customer phone number, deserves a second look.
Common stumbles
Posting noise. If every note goes to a busy channel, people will mute it. Use a mention word to filter, or send only to a dedicated channel.
Wrong list. Cards appear in the list you chose when you connected. If the board layout changes, update the workflow.
Plan access. Connectors depend on your plan. If you cannot find a connector, check that your plan includes it.
Private information. Do not send anything to a shared channel that the channel members should not read.
What Tom ended up with
Tom's setup is two small pieces. Every note goes to a team channel in Slack as a short summary. Any note that contains "callback" also makes a Trello card in his "To call" list. He reviews the card text once a day when he sits down with coffee. The retyping is gone.
Try it
Connect one destination in LetsVoice and test it with a single sample note before you point it at anything real.