Margaret Eneware
Customer support +CRM Professional
New to Contra
Margaret is building their profile!
✅ Today I Learned: Reading Zap History & Troubleshooting Errors in Zapier
I spent today’s session going deep into a part of Zapier most beginners skip: Zap History — where every automation run gets logged, and where you actually learn whether your automation is working or broken.
Here’s what I practiced:
✅ Located Zap History and understood why it was empty (Zaps must be published/live to log runs — testing alone doesn’t count)
✅ Published my HubSpot → Formatter → Paths → Email automation for the first time
✅ Hit and resolved a real account-level error (“confirm your email before enabling this Zap”) by verifying my Zapier account email
✅ Triggered the live Zap for real by updating a contact’s City field in HubSpot
✅ Found and opened the logged run in Zap History
✅ Read a run’s overall status (Successful / Error / Filtered–skipped)
✅ Opened individual steps and read “Data in” vs “Data out” to see exactly what data moved through each stage
✅ Confirmed Path A ran (City = New_York) while Path B correctly skipped (“rule not met”)
✅ Reviewed the technical Logs tab and understood HTTP status codes (200:OK = success)
✅ Learned how the Replay button re-runs a task without waiting for a new trigger
Skills Practiced:
• Zap publishing & activation
• Error diagnosis (account-level vs step-level)
• Reading trigger/action data (Data in / Data out)
• Interpreting HTTP status codes in automation logs
• Multi-path (conditional branching) automation logic
• Debugging workflow using Zap History
Tools Used:
• Zapier (Zap Editor, Zap History, Formatter by Zapier, Paths by Zapier, Email by Zapier)
• HubSpot (contact records, triggering live automations)
Every automation eventually breaks or needs checking — knowing how to read Zap History means I don’t panic when that happens. I know exactly where to look and what “healthy” vs “broken” looks like at every step.
0
2
Zapier Training Recap: Formatter, Paths & Email Automation
Today I went deeper into Zapier, Zapier’s no-code automation platform, working entirely from my phone. I extended a HubSpot-to-Email automation I’d already built by adding a data-formatting step and confirming my conditional logic and final email delivery all work correctly.
What I Practiced
✅ Added a Formatter by Zapier step to the automation, using the “Text” action event with a Capitalize transform
✅ Connected the Formatter step to pull in the Firstname field from a HubSpot contact
✅ Tested the Formatter step and confirmed it correctly capitalized the first letter of the name
✅ Placed the Formatter step before my existing Paths step, so data gets cleaned before the automation branches
✅ Re-tested my Path conditions step (City exactly matches “New_York”) and correctly interpreted a “path would not have continued” result when the test record’s city didn’t match
✅ Reviewed and confirmed the final Send Outbound Email step — recipient, subject line, and a dynamic body pulling in both Firstname and Email fields from HubSpot
✅ Ran a full test of the email step and confirmed successful delivery
✅ Made the intentional decision to keep the Zap unpublished while still testing and refining it
Skills Practiced
• Data transformation / text formatting in automation workflows
• Conditional logic (Paths) and interpreting automation test results
• Dynamic field mapping between connected apps
• End-to-end automation testing before going live
1
13
Learning Recap: Multi-Path Automation with Zapier Paths
Today I advanced my Zapier skills by learning Paths — a way to build automations that branch into different outcomes based on the data they receive, rather than following a single straight line.
What I Practiced
✅ Removed a single Filter step from an existing HubSpot automation
✅ Added a Paths by Zapier step in its place, splitting the workflow into two branches
✅ Configured Path A with a condition: only continue if Contact City exactly matches a specific value
✅ Configured Path B with the opposite condition: only continue if Contact City does not match that value
✅ Built a personalized email for Path A using dynamic contact data (first name and email)
✅ Built a separate, differently-worded personalized email for Path B using the same dynamic fields
✅ Ran live tests on both Path A and Path B to confirm each branch’s logic worked correctly
✅ Confirmed both email actions sent successfully during testing
Skills Practiced
• Conditional branching logic (multi-path automation)
• Rule-based decision making within a workflow
• Dynamic data personalization across multiple branches
• Live testing and validation of complex, multi-step automations
0
6
Learning Recap: Zapier + HubSpot Integration + Filters
Today I advanced my Zapier skills by connecting a real CRM (HubSpot) and learning how to add conditional logic to an automation, so it only runs when specific criteria are met.
What I Practiced
✅ Connected my real HubSpot account to Zapier, including authorizing app permissions
✅ Built a Trigger using HubSpot’s “Contact Recently Created or Updated” event
✅ Created a test contact in HubSpot to generate real sample data for the workflow
✅ Ran a live test on the Trigger step and confirmed it passed
✅ Added a Filter by Zapier step between the Trigger and Action, to control exactly when the automation continues
✅ Configured a filter condition (“Only continue if Contact City exactly matches a specific value”)
✅ Ran a live test on the Filter step and confirmed the condition passed correctly
✅ Configured an Email by Zapier action using dynamic data (contact’s first name and email) pulled automatically from HubSpot
✅ Ran a live test on the Action step and confirmed the email was sent successfully
✅ Cleaned up the workflow by removing an unused extra step, leaving a clean 3-step automation
Skills Practiced
• CRM integration and account authorization
• Multi-step workflow design (Trigger → Filter → Action)
• Conditional logic / rule-based automation
• Dynamic data mapping between connected apps
• Live testing and validation at every stage of a workflow.
0
6