This screenshot shows a complex Zapier automation (Zap) you created to streamline IT Change Requests by automatically creating Jira tickets and related actions across multiple systems based on spreadsheet inputs. Here’s a breakdown of what I've built:

⸻

🔁 Overview:

This Zap is triggered by changes in a Google Sheet (rows added or updated). Based on the data in that row, it branches into multiple paths to create Jira issues, send emails, and update StatusPage or NoOps systems depending on the change request type.

⸻

⚙️ Detailed Flow:

1. Trigger:

• Step 1: Watches for a new or updated row in a specific Google Sheet.

• Step 2: Looks up the row that triggered the zap to pull all necessary data.

• Step 3: A Filter determines if the data meets the condition to proceed (e.g. valid change request).

• Step 4: Paths split the flow into different automated outcomes depending on which type of request it is.

⸻

🔀 Paths:

🟦 Path A: Create ITCR Jira Ticket

• Step 5: Determines if this path is needed.

• Step 6: Finds the Jira user associated with the change.

• Step 7: Formats the data for consistency (e.g., timestamps, names).

• Step 8: Creates the Jira issue in the ITCR project.

• Step 9: Sends a confirmation or notification email via Gmail.

⸻

🟥 Path B: Create DBA Jira Ticket

• Step 10-14: Same flow as above, but creates a ticket in the DBA (DBOPS) Jira project. This supports the split of responsibilities between general IT and database operations.

⸻

🟨 Path C: Create StatusPage Post

• Steps 15-21: Prepares and posts a scheduled maintenance/update to StatusPage, including:

• Finding the correct component

• Formatting start, end, and completion times

• Creating the StatusPage post

• Sending notification email

⸻

🟧 Path D: Create NoOps Monitoring Ticket

• Steps 23-28: Creates a Jira issue for NoOps monitoring if applicable.

• Finds the user

• Formats the data

• Creates a Jira ticket specifically for monitoring tasks

⸻

🧠 Purpose:

This solution eliminates manual data entry and makes sure:

• The right teams are notified

• Jira issues are automatically generated with accurate data

• StatusPage is updated without delay

• Emails are sent to confirm each action

⸻

This automation demonstrates my expertise in process automation, Jira administration, and Zapier workflows. It directly supported deployment operations, change management, and cross-functional communication, saving hours of repetitive effort and reducing errors.