Step 1: Getting started
Note: The steps below include optional steps to attach the Asana link back to your original message and/or voice memo.
Trigger when “New AI Prompt Response Generated (only if not using template)
Setup
Configure
Step 2: Create and file a bug ticket in Asana as a new task
Step 2a
Step 2b
Setup
Configure
Steps to Reproduce: <”Ai Response Responses Json Steps to Reproduce” from Step 1>
Actual Result: <”Ai Response Responses Json Actual Results” from Step 1>
Expected Result: <”Ai Response Responses Json Expected Results” from Step 1>
Link to original message: <”Messages Message Link” from Step 1>
Created from Carbon Voice message sent by: <”Messages Creator Full Name” from Step 1>
DONE BY CARBON VOICE
FOR PAID ZAPIER ACCOUNTS
Step 3: Attaching link to Asana task: Adding different paths for voice memos versus messages in a conversation
Note: You can only add attachments to your own voice memos and messages. However, if you generate a bug report from a team member’s message, the automation creates two paths to ensure visibility: one for your voice memos and another for messages, including any that you didn’t post. For your voice memos, links can be attached directly. For other messages, the original message is forwarded back to the conversation with the link attached, ensuring that everyone can track and see the bugs being reported, and no ticket gets lost.
Add App: Paths by Zapier
Step 4: Path A - Path Conditions to Attach Asana Link to a Voice Memo
Type of Rule: Choose “Custom rules”
Only continue if:
<”Messages Message Type” from Step 1>
(Text) Contains
voicememo
Step 5: Path A - Add Asana Link to Carbon Voice Voice Memo
Setup
Configure
Step 6: Fallback - Path Conditions to forward message with Asana Link attached
Choose the type of rules to use for this path branch: Fallback
Step 7: Forward original Carbon Voice message to the same Conversation
Setup
Configure