Solutions Showcase: part 1 of 7
Browse case studies by tool and use case: automations, AI agents, dashboards, and custom platforms.
The complete text of the site in 7 parts, shortest case studies first. Parts:
Contents (every section and case study)
Custom SaaS Platforms
n8n Automations
Zapier Automations
Make Automations
Google Apps Script
Python Automation
AI Agents
AI Agents for WhatsApp
AI Agents for Ecommerce
ClickUp Setups
Monday.com Setups
Airtable
Power BI
Looker Studio
Dashboards & Reporting
Case studies in full
Skool to Slack, LeadConnector and Close Zap
This Zap connects Skool, Slack, LeadConnector and Close, starting when a member answers the Skool membership questions.
Section: Zapier Automations
Project Overview
This Zap connects Skool, Slack, LeadConnector, and Close. When a member answers the membership questions in Skool, the automation sends a message to a Slack channel, adds or updates the contact in LeadConnector, and looks up the matching contact and lead in Close.
Tools: Zapier, Skool, Slack, LeadConnector, Close.
01. How It Works
- Skool: Triggers when a member answers the membership questions.
- Slack: Sends a message to a Slack channel.
- LeadConnector: Adds or updates the contact.
- Close: Looks up the matching contact.
- Close: Looks up the matching lead.
Image: The five-step Zap: a Skool trigger, a Slack channel message, a LeadConnector contact update and two Close lookups.
02. Workflow Overview
Final Outcome
The Zap connects member responses in Skool with Slack notifications, LeadConnector contact management, and contact and lead lookups in Close.
Page · Plain text
BigQuery to Google Sheets Data Pipeline
Implemented a robust data pipeline using SyncWith and SQL to extract and sync data from BigQuery to Google Sheets for real-time analytics and reporting.
Section: Google Apps Script
Project Overview
This project uses SyncWith and SQL to extract and synchronize data from BigQuery to Google Sheets, supporting analytics and reporting.
Technology: Google Apps Script, BigQuery, Google Sheets, SQL, SyncWith
01. The Solution
A data pipeline was implemented using SQL queries and SyncWith to retrieve data from BigQuery and sync it into Google Sheets for reporting.
02. How It Works
- Query data in BigQuery using SQL.
- Join employer and sign-up data by month.
- Schedule the query to support regular KPI reporting.
- Sync the resulting data to Google Sheets.
03. Workflow
04. Implementation
The SQL query shown in the screenshot groups records by year and month and joins employer and sign-up data for KPI reporting.
Image: A scheduled BigQuery SQL query joining employer and sign-up data by month for the KPI sheet.
05. Outcome
The pipeline supports synchronized data reporting from BigQuery to Google Sheets, helping make KPI data available for analytics.
Page · Plain text
Gmail to ClickUp Zap
This Zap automates the process of task creation in ClickUp based on incoming emails from a specified sender in Gmail.
Section: Zapier Automations
Project Overview
This Zap connects Gmail with ClickUp to automate task creation from emails received from a specified sender. When a matching email arrives, the automation creates a new task in ClickUp and uploads any email attachments to that task.
Tools: Zapier, Gmail, ClickUp.
01. How It Works
- Incoming Email: Gmail receives an email from the designated sender.
- Create Task: Zapier automatically creates a new task in ClickUp based on the email.
- Upload Attachments: Any attachments included in the email are uploaded and attached to the newly created task.
Image: Zapier Automation
02. Workflow Overview
03. Key Benefits
- Automated task creation: Converts matching incoming emails into ClickUp tasks.
- Attachment handling: Keeps email attachments with the corresponding task.
- Centralized information: Consolidates task details and documents in ClickUp.
Final Outcome
The Zap streamlines email-based task creation by connecting Gmail and ClickUp, keeping relevant email information and attachments together in one task.
Page · Plain text
Google Apps Script for Chart Automation
Utilized Google Apps Script to automate the generation and saving of chart images to Google Drive, streamlining the reporting process.
Section: Google Apps Script
Project Overview
This project uses Google Apps Script to automate the generation of chart images and save them to Google Drive, streamlining the reporting process and reducing manual effort.
Technology: Google Apps Script, Google Drive
01. The Challenge
Generating chart images and saving them manually can add repetitive steps to the reporting process and make report preparation less efficient.
02. The Solution
A Google Apps Script automation was implemented to generate chart images and save them directly to Google Drive, simplifying chart management for reporting.
03. How It Works
- Generate chart images using Google Apps Script.
- Automate the chart image generation process.
- Save the generated images to Google Drive.
04. Workflow
05. Technology
- Google Apps Script: Automates chart image generation.
- Google Drive: Stores the generated chart images.
06. Outcome
The automation streamlines chart image generation and storage, reducing repetitive manual work in the reporting process.
Page · Plain text
Automated PDF Invoicing via Email
Created Google Apps Script to automatically format data into PDF invoices and send them via email, saving manual effort and enhancing operational efficiency.
Section: Google Apps Script
Project Overview
This project uses Google Apps Script to format data into PDF invoices and send them via email, reducing manual effort and improving operational efficiency.
Technology: Google Apps Script.
01. The Challenge
Preparing invoices manually involves formatting data into invoice documents and sending them to recipients by email. This process requires repetitive manual effort.
02. The Solution
A Google Apps Script solution was developed to automate invoice formatting, PDF generation, and email delivery.
03. How It Works
- Format invoice data: Google Apps Script formats the data into an invoice.
- Generate PDF: The formatted invoice is produced as a PDF.
- Send via email: The PDF invoice is sent through email.
04. Workflow
05. Technology
- Google Apps Script: Automates invoice formatting, PDF generation, and email delivery.
06. Outcome
The automation reduces manual invoicing effort by combining PDF invoice creation and email delivery into a scripted process.
Page · Plain text
Daily Slack Updates Make Scenario
The automation is designed to send daily updates to Slack. The data in Google Sheets is updated daily, and the KPI data is sent to Slack every day using a Make scenario.
Section: Make Automations
Project Overview
This Make scenario sends daily KPI updates to Slack using data from Google Sheets. The spreadsheet data is updated daily, and the scenario delivers the KPI information to Slack.
How It Works
1. Google Sheets Data
The scenario uses data from Google Sheets as the source for daily KPI updates.
2. Router
A Router splits the workflow into two separate branches.
3. Retrieve KPI Values
Each branch uses a Google Sheets module to retrieve the relevant range values.
4. Send Slack Updates
Each branch sends a message to Slack with the corresponding KPI information.
Image: Screenshot of working automation
Workflow Architecture
The workflow contains two branches, each connecting a Google Sheets module to a Slack message module.
Tools and Integrations
- Make: Connects the modules and manages the workflow.
- Google Sheets: Provides the KPI data.
- Slack: Receives the daily updates.
Outcome
The scenario automates the delivery of daily KPI updates from Google Sheets to Slack, reducing the need to share these updates manually.
Page · Plain text
Google Sheets Data Visualization Dashboard
Created an interactive dashboard within Google Sheets for effective data visualization and tracking, serving as a quick reference tool for stakeholders.
Section: Google Apps Script
Project Overview
This project uses Google Sheets to present CRM data in a dashboard format, giving stakeholders a quick reference for hiring totals, job closures, and feedback scores.
Technology: Google Sheets, Google Apps Script
01. The Solution
An interactive dashboard was created within Google Sheets to organize key metrics and make performance data easier to review.
02. Dashboard Metrics
- Total average responses
- Total bad responses
- Total employers who hired through Taraki
- Total jobs of employers who hired through Taraki
- Total hired
- Total jobs closed
- Experience with Taraki
- Good feedback
- Average feedback
- Bad feedback
03. Implementation
The dashboard uses Google Sheets formulas to calculate and display metrics from multiple data tabs, providing a consolidated view of hiring activity and feedback.
Image: A CRM dashboard inside Google Sheets tracking hiring totals, job closures, and feedback scores.
04. Outcome
The dashboard serves as a quick reference for stakeholders to track hiring activity, job closures, and feedback scores in one place.
Page · Plain text
Integration of RB2B with Go High Level and Beehiv
RB2B is a platform that collects website visitor profiles.
Section: Make Automations
Project Overview
This automation connects RB2B, GoHighLevel, and Beehiiv through Make. When RB2B creates a website visitor profile, the profile is added to GoHighLevel as a contact, a deal is created for that contact, and the associated email is added to Beehiiv as a subscriber.
The Workflow
1. Website Visitor Profile
RB2B collects website visitor profiles and triggers the automation when a new profile is created.
2. Create a Contact in GoHighLevel
The visitor profile is added to GoHighLevel as a contact.
3. Create a Deal
A deal is also created in GoHighLevel for the new contact.
4. Add a Beehiiv Subscriber
The associated email address is added to Beehiiv as a subscriber.
Image: Screenshot of working automation in make.com
Platforms Used
- Make: Connects the platforms and automates the workflow.
- RB2B: Collects website visitor profiles.
- GoHighLevel: Stores the contact and its associated deal.
- Beehiiv: Receives the email address as a subscriber.
Outcome
The workflow automates the transfer of visitor profile information into GoHighLevel and adds the associated email address to Beehiiv, connecting contact and deal creation with subscriber addition.
Page · Plain text
Growth Model Development with Defined KPIs
Designed a dynamic growth model in Google Sheets, complete with Key Performance Indicators (KPIs) to enhance visibility and guide decision-making.
Section: Google Apps Script
Project Overview
This project uses Google Sheets to organize growth metrics and track performance across awareness, engagement, and retention.
Technology: Google Sheets, Google Apps Script
01. The Solution
A growth model was designed in Google Sheets with defined KPIs to improve performance visibility and support decision-making.
02. Key Metrics
- Awareness: Cumulative installs, cumulative signups, current installed audience, total installs, uninstalls, and reinstalls.
- Engagement: First-time installs, signups, conversion, new engaged users, total engaged users, job applications, and job applicants.
- Retention: Retained users, new retained users, retention percentages, and old retained users.
03. How It Works
The model organizes KPIs by growth funnel stage and displays results month over month, making it easier to review changes in performance over time.
Image: The growth funnel model: awareness, engagement, and retention KPIs tracked month over month.
04. Outcome
The growth model provides a consolidated view of awareness, engagement, and retention KPIs to enhance visibility and guide decision-making.
Page · Plain text
Batch Management of Access
The script reads from a spreadsheet cell that lists email addresses authorized for file access.
Section: Google Apps Script
Project Overview
This project uses Google Apps Script and Google Drive to manage file and folder access based on email addresses listed in a spreadsheet.
Technology: Google Apps Script, Google Drive
01. The Challenge
Managing access manually can make it difficult to keep file and folder permissions aligned with the current list of authorized users.
02. The Solution
A Google Apps Script automates access management by granting permissions to email addresses listed in the spreadsheet and removing access for addresses that are no longer listed.
03. How It Works
- Read authorized email addresses from a spreadsheet cell.
- Update sharing permissions for designated Google Drive files and folders.
- Grant access to listed email addresses.
- Remove access from addresses not currently listed.
- Support different access requirements for team members and clients.
04. Workflow
05. Technology
- Google Apps Script: Automates access and permission management.
- Google Drive: Stores the files and folders whose access is managed.
06. Outcome
The automation simplifies permission management and helps keep file access aligned with the authorized email list, reducing the risk of unauthorized viewing or editing.
Page · Plain text
Integration of Go High Level with Beehiv
This scenario is implemented so that whenever the status of an opportunity is changed in Go High Level, the associated email is added to Beehiv as a subscriber.
Section: Make Automations
Project Overview
This automation connects GoHighLevel and Beehiiv through Make. When an opportunity’s status changes in GoHighLevel, the associated email address is sent to Beehiiv and added as a subscriber.
The Solution
The Make scenario automates the transfer of contact email information between GoHighLevel and Beehiiv when an opportunity status changes.
How It Works
- Opportunity Status Changes: The scenario responds when an opportunity’s status is changed in GoHighLevel.
- Process the Contact Information: Make handles the information associated with the opportunity.
- Add the Subscriber to Beehiiv: The associated email address is added to Beehiiv as a subscriber.
Image: Screenshot of working automation from make.com
Platforms Used
- Make: Connects the two platforms and runs the automation.
- GoHighLevel: Provides the opportunity status change that triggers the scenario.
- Beehiiv: Receives the associated email address as a subscriber.
Outcome
The integration automates adding email addresses to Beehiiv following opportunity status changes in GoHighLevel, reducing the need to transfer subscriber information manually
Page · Plain text
Trello Cards to AI Social Captions and Hashtags Zap
This Zap runs every day, goes through the cards on a Trello board, and uses ChatGPT to write a social media caption and hashtags that are saved on each Trello card.
Section: Zapier Automations
Project Overview
This Zap runs daily, retrieves cards from a single Trello pillar, and uses ChatGPT to generate a social media caption and hashtags for each card. The generated content is then saved back to the corresponding Trello card.
Tools: Zapier, Trello, OpenAI (ChatGPT).
01. How It Works
- Daily Schedule: Schedule by Zapier starts the workflow once a day.
- Retrieve Cards: The Zap gets cards from a single Trello pillar.
- Loop Through Cards: Itemizer splits the cards into individual items so the subsequent steps run for each card.
- Check Each Card: A webhook GET request, Formatter utility step, and filter determine which cards continue.
- Read Attachments: The workflow retrieves the card’s attachments from Trello.
- Generate Captions and Hashtags: ChatGPT generates the social media caption and hashtags.
- Update Trello: The generated caption and hashtags are saved to the corresponding card.
Image: Zapier workflow pipeline
02. Workflow Overview
03. Final Outcome
The Zap automates caption and hashtag generation for Trello cards, saving the generated content directly to each card and reducing the need to write this content manually.
Page · Plain text
Google Calendar to ClickUp Zap
This Zap facilitates seamless integration between Google Calendar and ClickUp, enhancing task management and operational efficiency.
Section: Zapier Automations
Project Overview
This Zap connects Google Calendar with ClickUp. Whenever a new event is created in Google Calendar, the automation creates a corresponding task in ClickUp and transfers relevant event details, including the date, time, and description.
The Zap also assigns tasks to specific individuals to support task allocation and coordination.
Tools: Zapier, Google Calendar, ClickUp.
01. How It Works
- New Calendar Event: A new event is created in Google Calendar.
- Create ClickUp Task: Zapier automatically creates a corresponding task in ClickUp.
- Transfer Event Details: The task includes the event date, time, and description.
- Assign Task: The task is assigned to the specified individual.
02. Key Benefits
- Automated task creation: Converts new calendar events into ClickUp tasks.
- Information transfer: Carries relevant event details into ClickUp.
- Task assignment: Assigns tasks to specific individuals.
- Improved coordination: Connects calendar events with task management.
03. Workflow Overview
Final Outcome
The Zap integrates Google Calendar with ClickUp to automate task creation from new calendar events, transfer relevant event information, and assign tasks to the appropriate individuals.
Page · Plain text
TidyCal Booking to LeadConnector and Google Sheets Zap
This Zap runs when a new booking is made in TidyCal, adds or updates the contact in LeadConnector, and records the booking in Google Sheets.
Section: Zapier Automations
Project Overview
This Zap connects TidyCal, LeadConnector, and Google Sheets. When a new booking is made in TidyCal, the automation adds or updates the contact in LeadConnector and records the booking in Google Sheets.
The workflow includes filtering, text formatting, a spreadsheet lookup, and two paths to update an existing row or create a new one.
Tools: Zapier, TidyCal, LeadConnector, Google Sheets.
01. How It Works
- New Booking: A new booking in TidyCal triggers the Zap.
- Filter and Format: Filter by Zapier checks conditions, and Formatter processes text.
- Update Contact: LeadConnector adds or updates the contact.
- Find Spreadsheet Row: Google Sheets looks up the matching row.
- Route the Booking: The workflow splits into two paths: one updates the existing row, and the other creates a new row.
Image: The ten-step Zap: a TidyCal booking trigger, filter and text formatting, LeadConnector, a Google Sheets lookup, and two paths that update or create a row.
02. Workflow Overview
03. Final Outcome
The Zap connects booking management, contact updates, and spreadsheet records in one workflow, with separate paths for updating an existing Google Sheets row or creating a new one.
Page · Plain text
Cancel Calendly Bookings Zap
This Zap streamlines the process of appointment cancellations by integrating ClickUp with Calendly.
Section: Zapier Automations
Project Overview
This Zap integrates ClickUp with Calendly to streamline appointment cancellations. When a cancellation is initiated from within ClickUp by pressing the cancel button on a specific task, the corresponding appointment is automatically cancelled in Calendly.
The automation helps manage appointment slots, keep scheduling information updated, and reduce manual oversight.
Tools: Zapier, Calendly, ClickUp.
01. How It Works
- Initiate Cancellation: A user presses the cancel button on a specific task in ClickUp.
- Trigger the Zap: Zapier processes the cancellation workflow.
- Cancel the Appointment: The corresponding appointment is automatically cancelled in Calendly.
Image: Active Zapier Workflows for ClickUp-to-Calendly Cancellation Sync
02. Key Benefits
- Automated cancellations: Cancels the relevant Calendly appointment through ClickUp.
- Efficient scheduling: Helps keep appointment slots updated.
- Reduced manual work: Minimizes the need to cancel appointments manually in Calendly.
- Fewer scheduling conflicts: Helps keep cancellations synchronized between the platforms.
03. Workflow Overview
Image: Active ZapierAutomation
Final Outcome
The Zap connects ClickUp and Calendly to automate appointment cancellations initiated from ClickUp, simplifying scheduling management and reducing manual effort.
Page · Plain text
Integrating GoHighLevel with Beehiv Using Zapier
A Zap is being built to connect GoHighLevel with Beehiv.
Section: Zapier Automations
Project Overview
This project connects GoHighLevel with Beehiiv using Zapier. When a user submits a form on GoHighLevel, the submitted information is sent to a Zapier webhook and then added to Beehiiv.
The integration uses a GoHighLevel workflow to send the form data to Zapier, which receives the information and forwards it to Beehiiv.
Tools: Zapier, GoHighLevel, Beehiiv.
01. The Business Requirement
The objective is to connect GoHighLevel form submissions with Beehiiv so that submitted user information can be transferred between the two platforms through an automated workflow.
02. The Solution
A Zapier integration is being built to connect GoHighLevel with Beehiiv.
The process consists of the following steps:
- A user submits a form on GoHighLevel.
- A workflow in GoHighLevel sends the submitted information to a Zapier webhook.
- Zapier receives the information from the webhook.
- Zapier adds the received information to Beehiiv.
03. Project Snapshot
| Item | Detail |
|---|
| Automation platform | Zapier |
| Source platform | GoHighLevel |
| Destination platform | Beehiiv |
| Trigger event | GoHighLevel form submission |
| Data transfer | GoHighLevel workflow to Zapier webhook |
| Final action | Add submitted information to Beehiiv |
04. Workflow Architecture
05. Final Outcome
The integration is being built to transfer information submitted through GoHighLevel forms into Beehiiv using Zapier as the connection between the platforms.
Page · Plain text
Monday.com Timeline Stage Alerts to Slack and Close Zap
This Zap watches the timeline stages of Monday.com items and notifies the team in Slack each time an item reaches a new stage.
Section: Zapier Automations
Project Overview
This Zap monitors timeline stages for items in monday.com. When an item reaches a milestone, it updates the item and notifies the team in Slack. At the 45-days-left stage, it also checks Close for the opportunity and updates an existing opportunity or creates a new one when needed.
01. How It Works
- Webhook Trigger: Starts when an item reaches a timeline stage.
- Find Item: Looks up the item in monday.com.
- Determine Stage: Uses Python in Code by Zapier to identify the stage.
- Branch by Stage: Paths route the Zap according to the timeline milestone.
- Update and Notify: Updates the monday.com item and sends a Slack message.
- Close Integration: At 45 days left, checks Close and updates or creates an opportunity.
02. Timeline Milestones
The workflow handles these programme stages:
- 90 days in
- 60 days in
- 45 days in
- 60 days left
- 45 days left
- 1 day left
Image: Steps 1–16 and 31–33: the webhook trigger, the monday.com lookup, the Python step, and the Paths that update items and notify Slack.
03. Workflow Overview
At the 45-days-left stage, the workflow also checks Close and creates or updates an opportunity as needed.
Final Outcome
The Zap automates timeline-stage updates and team notifications, while supporting opportunity management in Close at the 45-days-left stage.
Image: Steps 17–30: the Close branches that find contacts and create leads and opportunities, each ending in a Slack message.
Page · Plain text
Batch Creation of Folders and Files
The script initiates by creating a structured main folder in Google Drive.
Section: Google Apps Script
Project Overview
This project uses Google Apps Script to create a structured folder hierarchy in Google Drive, generate spreadsheet files from templates, duplicate Google Docs templates, and record the created files and folders in a master spreadsheet.
Technology: Google Apps Script, Google Drive
01. The Challenge
Creating folders and preparing multiple files manually for each client requires repetitive work and makes file organization more time-consuming.
02. The Solution
A Google Apps Script automates folder creation, spreadsheet generation from templates, and duplication of Google Docs templates. A master spreadsheet records the names, IDs, and direct links of the created items.
03. How It Works
- Create a main folder in Google Drive.
- Generate predefined subfolders within it.
- Create spreadsheet files from templates in the relevant folders.
- Duplicate Google Docs templates and place them in their respective folders.
- Update the master spreadsheet with file and folder names, IDs, and links.
04. Workflow
05. Technology
- Google Apps Script: Automates the batch creation process.
- Google Drive: Stores the folders, spreadsheets, and duplicated documents.
06. Outcome
The automation streamlines the creation and organization of client folders and files while maintaining a master spreadsheet for easy navigation.
07. Implementation
Batch-Creation Script: Generates each client's folder structure, contract, and accounting files from templates.
Image: The batch-creation script that generates each client’s folder structure, contract, and accounting files from templates.
Page · Plain text
Automation of Shopify Orders to Google Sheets for Dropshipping E-commerce Store
The primary goal of this automation is to streamline the process of managing Shopify orders by automatically distributing them to the appropriate fulfillment sheets.
Section: Make Automations
Project Overview
This Make automation streamlines Shopify order management for a dropshipping e-commerce store. It records incoming orders, identifies the relevant products, and distributes order information to the appropriate Google Sheets fulfillment sheets based on supplier requirements.
How It Works
1. Shopify Order Tracking
When a new order is created in Shopify, the automation adds the order to a Make Data Store for tracking.
2. Product Identification
The workflow checks product IDs against a Google Sheets database to determine which supplier's fulfillment sheet should receive the order.
3. Master Sheet Integration
A master sheet consolidates order information. Changes made to the master sheet are reflected in the respective Google Sheets to maintain consistency.
4. Supplier-Based Order Distribution
Order details are routed to the appropriate fulfillment sheets so that each supplier receives the relevant order information.
Workflow Architecture
A master sheet serves as the central location for consolidating and managing order information.
Tools and Integrations
- Make: Automates the workflow and coordinates data between applications.
- Shopify: Provides order and product information.
- Google Sheets: Stores product IDs, consolidates order data, and supports supplier-specific fulfillment tracking.
Outcome
The automation helps organize Shopify orders, distribute them according to supplier requirements, and keep order information consistent across the relevant Google Sheets.
Page · Plain text
Project Tracker Management
Worked on developing a Project Tracker in Google Sheets to allocate tasks, track project milestones, and monitor team performance, complete with real-time updates and visual dashboards for easy interpretation.
Section: Google Apps Script
Project Overview
This project involved developing a Project Tracker in Google Sheets to help manage tasks, monitor project milestones, and track team performance. The tracker includes real-time updates and visual dashboards for easier interpretation of project schedules and progress.
Tools: Google Apps Script and Google Sheets.
01. Project Objectives
The tracker was developed to support three main activities:
- Task Allocation: Organize and allocate project tasks.
- Milestone Tracking: Track project milestones and schedules.
- Team Performance Monitoring: Monitor team performance through the tracker.
02. The Solution
A project tracking system was developed in Google Sheets, with real-time updates and visual dashboards to make project information easier to understand.
03. Project Schedule Visualization
The tracker includes a Gantt-style project schedule generated directly in Google Sheets. The schedule displays task start and end dates across a timeline, making it easier to view project durations and overlapping activities.
Image: A Gantt-style project schedule generated directly in Google Sheets.
04. Key Features
- Task allocation and organization
- Project milestone tracking
- Team performance monitoring
- Real-time updates
- Visual dashboards for interpreting project information
- Gantt-style schedule visualization in Google Sheets
05. Tools and Technologies
- Google Sheets: Provides the project tracking spreadsheet, schedule, and visual dashboard.
- Google Apps Script: Listed as a technology used in the project.
06. Outcome
The Project Tracker provides a centralized way to allocate tasks, track milestones, and monitor team performance through Google Sheets, supported by visual scheduling and dashboard features.
Page · Plain text
Automation of ClickUp and Google Sheets
This Make scenario is implemented whenever a task gets completed in ClickUp.
Section: Make Automations
Project Overview
This Make automation connects ClickUp with Google Sheets to transfer completed task details into the appropriate spreadsheet. When a task is completed in ClickUp, the scenario processes its information and uses custom fields to determine which Google Sheets file should receive the data.
The Business Need
Task information needs to be recorded in the relevant Google Sheets file when work is completed in ClickUp. This scenario automates that transfer and routes the data according to the task's custom fields.
The Solution
The Make scenario uses a custom webhook, variable configuration, and a router to direct information into Google Sheets.
- Webhooks: Receives data through a custom webhook.
- Tools: Sets multiple variables used during processing.
- Router: Splits the workflow into two branches.
- Google Sheets: Each branch adds a row to a spreadsheet.
How It Works
1. Receive the Webhook
The workflow starts when the custom webhook receives the task information.
2. Set Variables
The Tools module sets multiple variables that are used in the subsequent workflow steps.
3. Route the Data
The Router divides the workflow into two branches. The routing logic uses the task's custom fields to determine the appropriate destination.
4. Add a Row to Google Sheets
Each branch connects to a Google Sheets module configured to add a row to its respective spreadsheet.
Image: Screenshot of working automation in make.com
Workflow Architecture
The router splits the workflow into two Google Sheets branches, allowing data to be directed to the relevant destination.
Tools and Integrations
- Make: Connects the workflow modules and manages routing.
- ClickUp: Provides the completed task information.
- Google Sheets: Receives task details as new spreadsheet rows.
Outcome
The scenario automates the transfer of completed task information into Google Sheets and routes the data according to custom fields, reducing the need to enter the same information manually.
Page · Plain text
Trello to Facebook, LinkedIn and Instagram Social Posting Zap
This Zap runs every day, picks up the Trello cards for that day, and publishes their images and captions to Facebook, LinkedIn and Instagram.
Section: Zapier Automations
Project Overview
This Zap automates social media publishing using Trello and Zapier. It runs daily, retrieves the Trello cards scheduled for that day, and publishes their images and captions to Facebook, LinkedIn and Instagram.
Each Trello card contains the images and platform-specific captions, allowing content to be prepared in Trello before publication.
Tools: Zapier, Trello, Facebook, LinkedIn, Instagram.
01. How It Works
- Daily Schedule: Schedule by Zapier starts the workflow once a day.
- Retrieve Trello Cards: The Zap gets cards from a single Trello pillar, splits them into individual items and loops through them.
- Check Card Details: Formatter steps convert start and due dates and read the card status. A filter determines which cards continue.
- Extract Content: The workflow extracts social media captions and retrieves image attachments from Trello.
- Update Trello: The card is updated and moved to another list.
- Publish to Social Platforms: Code by Zapier and Paths route the content according to platform and content type.
Image: Steps 1–11: the daily schedule, the Trello card lookup, a loop over each card, and date and status formatting.
Image: Steps 12–48: caption extraction, Trello updates, and the Paths that publish to Facebook Pages, LinkedIn and Instagram for Business.
02. Platform Publishing
- Facebook: Publishes posts and videos to Facebook Pages.
- LinkedIn: Publishes company updates.
- Instagram: Publishes photos and videos to Instagram for Business.
03. Workflow Overview
04. Workflow Screenshots
- Steps 1–11: Daily schedule, Trello card lookup, loop over cards, and date and status formatting.
- Steps 12–48: Caption extraction, Trello updates, and publishing paths for Facebook Pages, LinkedIn and Instagram for Business.
Final Outcome
The Zap automates daily social media publishing from Trello, using prepared images and platform-specific captions to publish content across Facebook, LinkedIn and Instagram.
Page · Plain text
CSV-Based Inventory Data Entry Automation
Created a script to automate data entry in an inventory sheet from CSV files.
Section: Google Apps Script
Project Overview
This project uses Google Apps Script to automate the import of inventory data from CSV files into an inventory sheet. It also includes a data-cleaning function to help maintain the accuracy and integrity of imported information.
Technology: Google Apps Script.
01. The Challenge
Inventory data from multiple warehouses can contain inconsistencies that need to be identified during processing. The provided inventory sheet shows examples of data-quality issues, including mismatched warehouse locations and unidentified SKUs.
02. The Solution
A Google Apps Script was created to automate CSV-based inventory data entry. The script also includes a data-cleaning function to help ensure that imported data is accurate and consistent.
03. How It Works
Step 1: Import Inventory Data
The script automates data entry into the inventory sheet using CSV files as the data source.
Step 2: Clean the Imported Data
A data-cleaning function processes the imported data to help maintain accuracy and integrity.
Step 3: Identify Inventory Issues
The inventory sheet displays problems such as mismatched locations and unidentified SKUs, helping highlight records that require attention.
04. Google Sheets Custom Menu
The provided screenshot shows a custom menu in Google Sheets with two options:
- Update Inventories
- Add Leading Zeros
These options provide menu-based access to the inventory-related script functions.
05. Example: Inventory Data Quality
The inventory sheet contains warehouse names, SKUs, locations, updated on-hand quantities, and a Problems column. The displayed examples include mismatched location information and unidentified inventory records.
Image: Multi-warehouse inventory data with flagged data-quality issues the cleaning step catches: mismatched locations and unidentified SKUs.
06. Technology
- Google Apps Script: Automates CSV-based inventory data entry and provides a data-cleaning function.
- Google Sheets: Holds the inventory data and displays inventory records and flagged issues.
07. Outcome
The solution automates inventory data entry from CSV files and includes data cleaning to support accurate and consistent inventory records.
Page · Plain text
Daily Ticket-Count Automation: Gmail PDFs to BigQuery and Google Sheets
A Python job that reads daily Ticketmaster audit PDFs from email, stores every figure in BigQuery and publishes a Google Sheet that mirrors the team’s existing workbook.
Section: Python Automation
Project Overview
A Python job reads daily Ticketmaster audit PDFs received by email, stores the extracted figures in BigQuery, and publishes a Google Sheet that mirrors the team's existing workbook.
Technology: Python, Gmail API, BigQuery, Google Sheets API, PDF parsing, pytest
01. The Problem
An events company received daily Ticketmaster audit PDFs by email and manually re-entered the reported figures into a workbook. This repetitive process required daily manual effort.
02. The Solution
A scheduled Python job uses the Gmail API and an OAuth refresh token to retrieve report emails, download and parse PDF attachments, store the figures in BigQuery, and publish the results to Google Sheets.
03. How It Works
- Retrieve report emails using the Gmail API.
- Download the attached Ticketmaster audit PDFs.
- Parse the PDFs and extract ticket-count figures.
- Store the extracted figures in BigQuery.
- Publish a Google Sheet that mirrors the existing workbook.
- Record each job run in the Run Log tab.
04. Workflow
05. Google Sheets Output
The published spreadsheet tracks:
- General Admission (GA) tickets
- VIP tickets
- Total tickets
- Tickets sold against capacity
- Percentage sold
Image: The Google Sheet the job publishes: tickets sold per day against capacity, split into GA and VIP, with the percentage sold. Event names and some tab names are hidden.
The workbook includes a Top Sheet, Raw Data, and Run Log tabs.
06. Testing and Implementation
The project followed a specification-first process: design specification, implementation plan, tests using fixture PDFs, and then the pipeline implementation.
Image: The project repository, with the ticket-count source code, tests, scripts and design documents.
The repository includes the ticket-count source code, scripts, tests, and design documents.
07. Outcome
The job automates the transfer of ticket figures from daily email attachments into BigQuery and Google Sheets, reducing manual data entry and providing a run log for tracking executions.
Image: The Run Log tab, with one row for each run of the job and its time.
Page · Plain text
TikTok Video Downloader without watermark: Save Any Reel Directly to Google Drive
To automatically download a TikTok video and store it in Google Drive with a public share link.
Section: AI Agents
TikTok Video Downloader: Save Videos Directly to Google Drive
Automatically download TikTok videos without a watermark and save them to Google Drive with a shareable link.
Category: AI Agents Tools: TikTok, Google Drive
1. Project Overview
This workflow automates the process of fetching a TikTok video, extracting its direct video URL, downloading the video, and uploading it to Google Drive. It simplifies video collection for content management and reposting workflows.
2. The Challenge
Saving videos manually requires opening the video page, locating the downloadable video, downloading the file, and uploading it to cloud storage. These repeated steps take time and make organizing video assets less convenient.
3. The Solution
A workflow connects TikTok video-page processing with automated downloading and Google Drive storage. It extracts the direct video URL, downloads the video file, and uploads it to Drive, where a shareable link can be generated.
4. How the Workflow Works
Image: n8n workflow
- Manual Trigger: Start the workflow with a single click.
- Fetch Video Page: Retrieve the TikTok page information.
- Extract Video URL: Process the page data to identify the direct video link.
- Download Video: Use the extracted URL to download the video file.
- Upload to Google Drive: Store the downloaded video in Drive.
- Generate Shareable Link: Configure the uploaded file for public access and create a link for sharing.
5. Workflow
6. Key Features
- One-Click Execution: Start the process manually.
- Automated URL Extraction: Identify the direct video link from page data.
- Automated Downloading: Retrieve the video file through the extracted URL.
- Cloud Storage: Save downloaded videos directly to Google Drive.
- Shareable Links: Make the file accessible through a configured sharing link.
7. Business Value
The workflow reduces repetitive downloading and uploading tasks, helping users organize video assets and make them available for sharing from Google Drive.
8. Final Outcome
A streamlined workflow that connects TikTok video retrieval with automated downloading, Google Drive storage, and shareable links—reducing manual effort in video collection and management.
Page · Plain text
Email Reminder System
The script is scheduled to run daily to ensure real-time relevancy of its functions.
Section: Google Apps Script
Project Overview
This project uses Google Apps Script to check dates stored in linked spreadsheets and send customized email reminders when tasks or events are due. The scripts support daily reminders, due-diligence checkups, and individual screening workflows.
Technology: Google Apps Script
01. The Challenge
Manually checking multiple spreadsheets for due dates and sending reminders can be time-consuming and may lead to missed tasks or delayed communications.
02. The Solution
Google Apps Script automates the process of locating linked spreadsheets, reading date-specific data, comparing stored dates with the current date, and sending email reminders when the required conditions are met.
03. How It Works
- Run the script on a daily schedule.
- Extract spreadsheet links from a master file.
- Open the relevant spreadsheet and read its date-specific data.
- Compare stored dates with the current date.
- Send customized email reminders when a matching date is found.
04. Workflow
05. Implementation Examples
Example 1: Extracting Spreadsheet Links
The script checks spreadsheet cells for hyperlinks, extracts the target URL, and locates the appropriate file before processing its data.
Image: Extracting a hyperlink from a spreadsheet cell to locate the right file before checking its dates.
Example 2: Due-Diligence Email Reminders
The due-diligence script compares the current date against spreadsheet data and sends a compliance-related email when the required date conditions are met.
Image: A due-diligence checkup variant: comparing today’s date against the sheet before sending a scheduled compliance email.
Example 3: Individual Screening Automation
The screening script iterates through rows in the master sheet, checks confirmation values, extracts linked spreadsheet URLs, and processes the corresponding files.
Image: The companion screening script that walks each row and extracts the linked spreadsheet before processing it.
06. Technology
Google Apps Script: Automates scheduled execution, spreadsheet link extraction, date comparisons, and email notifications.
07. Outcome
The automation reduces repetitive spreadsheet checks and helps maintain consistent communication by sending reminders when the specified date conditions are satisfied.
Page · Plain text
Integration of Shopify and ClickUp for Managing Refunded Orders
This scenario is built so that whenever there is a refunded order in Shopify, the order details are added to ClickUp as tasks.
Section: Make Automations
Project Overview
This Make automation connects Shopify with ClickUp to help manage refunded orders. When an order is refunded in Shopify, the scenario retrieves the order details and uses them in the ClickUp task-management workflow.
The integration brings refunded-order information into ClickUp, making it easier for the team to manage refund-related tasks in one place.
The Business Need
Refunded orders need to be identified and their details made available for follow-up. Without an automated connection between Shopify and ClickUp, the team may need to transfer order information manually when managing refunded orders.
The Solution
The Make scenario connects Shopify and ClickUp through an automated workflow.
- Shopify trigger: Starts the scenario when a new event is detected.
- Get an order: Retrieves the relevant order details from Shopify.
- Data Store: Searches for a matching record as part of the workflow.
- ClickUp: Updates a task with custom fields using the available information.
- Tools: Includes a sleep step before the final Data Store action.
- Data Store cleanup: Deletes a record at the end of the scenario.
How It Works
1. Shopify Event
The workflow begins with a Shopify event that triggers the scenario.
2. Retrieve Order Information
The Shopify module retrieves the order details needed for the next steps.
3. Search the Data Store
The scenario searches the Data Store for a relevant record before continuing.
4. Update ClickUp
The ClickUp module edits a task using custom fields, connecting the order information with the task-management process.
5. Execute Follow-up Actions
A Tools sleep step runs before the final Data Store module deletes a record.
Image: Screenshot of working automation from make.com
Workflow Architecture
Tools and Integrations
- Make: Connects the applications and runs the scenario.
- Shopify: Provides the order event and order details.
- ClickUp: Manages tasks using custom fields.
- Data Store: Supports record searching and deletion.
Outcome
The scenario connects Shopify order events with ClickUp task updates and Data Store operations. Its purpose is to streamline the handling of refunded-order information by bringing these steps into one automated workflow.
Page · Plain text
YouTube Video Details Scraper using Automation
Automatically collect detailed info from YouTube videos of popular creators for content analysis.
Section: AI Agents
YouTube Video Details Scraper Using Automation
Automating YouTube video data collection and storing results in Airtable for content research and analysis.
Category: AI Agents Integrations: YouTube, Airtable, Apify
01. Project Overview
This workflow automates the collection of detailed information from YouTube videos. It retrieves video links from Airtable, sends them to a scraping service, waits for the results, and updates the corresponding Airtable records with the collected data.
02. The Challenge
Collecting video information manually can be time-consuming, especially when researching multiple creators and videos. Titles, channel details, view counts, likes, descriptions, subtitles, and thumbnails must be gathered and organized before they can be analyzed.
03. The Solution
An automated workflow connects Airtable with a video-scraping service. It processes video links, retrieves available video details, and saves the results back to Airtable, reducing repetitive manual data collection.
04. How It Works
Image: n8n working flow screenshot
Step 1 — Manual Trigger: Start the workflow by clicking the test or run button.
Step 2 — Fetch Airtable Records: Search Airtable for records containing YouTube video links ready for processing.
Step 3 — Run the Scraper: Send the video information to the Apify API to start the scraping actor.
Step 4 — Wait for Completion: Allow the scraper to finish collecting the available video details.
Step 5 — Retrieve Results: Fetch the completed scraping results from the actor.
Step 6 — Update Airtable: Write the collected information back to the corresponding Airtable record.
05. Workflow
06. Data Collected
Depending on availability from the scraper, the workflow can collect:
- Video title and channel name
- Views and likes
- Video description and subtitles
- Thumbnail information
07. Business Value
- Less manual work: Automates repetitive video research.
- Organized data: Keeps collected information in Airtable.
- Scalable collection: Supports processing multiple video records.
- Simplified analysis: Makes video information easier to review and compare.
08. Final Outcome
The workflow connects Airtable and Apify to automate YouTube video data collection, helping organize video information in a structured database for content research and analysis.
Page · Plain text
Looker Studio: Google Ads Dashboard
A Looker Studio dashboard tracking Google Ads cost, revenue, orders, profit and ROAS for the same multi-channel account.
Section: Looker Studio
Looker Studio: Google Ads Dashboard
A Looker Studio dashboard that brings Google Ads cost, revenue, orders, profit, and ROAS into one reporting view.
Technology: Looker Studio, Google Ads
01. Project Overview
This project adds a dedicated Google Ads dashboard to an existing multi-channel paid media reporting setup. It brings key advertising and financial metrics together so teams can review campaign performance without relying on separate exports.
02. The Challenge
Reviewing Google Ads performance requires monitoring multiple metrics, including advertising spend, revenue, orders, clicks, and conversion rate. When these figures are viewed separately, it becomes harder to assess campaign performance and understand the relationship between advertising costs and revenue.
03. The Solution
A dedicated Google Ads report was created in Looker Studio to consolidate the main performance metrics into one dashboard.
The dashboard includes:
- Cost and Revenue: Review advertising spend alongside generated revenue.
- Google Ads Revenue: Track revenue attributed to Google Ads.
- Orders: Monitor order volume.
- Profit and Profit Margin: Review profitability alongside advertising costs.
- Clicks and Conversion Rate: Evaluate traffic and conversion performance.
- CPP, AOV, and ROAS: Monitor cost per purchase, average order value, and return on ad spend.
- Date Filtering: Review results for a selected reporting period.
04. Dashboard Overview
The dashboard presents KPI cards at the top, followed by a time-series chart showing performance over the selected period. This layout makes it easier to scan key figures and compare cost and revenue trends.
Image: Google Ads dashboard for the same account: cost, revenue, orders, profit and ROAS alongside clicks and conversion rate.
The dashboard includes cost, revenue, orders, profit, profit margin, clicks, conversion rate, CPP, AOV, and ROAS.
05. Technology and Integration
- Looker Studio: Dashboard creation and performance reporting.
- Google Ads: Advertising performance data.
The report provides a consolidated view of paid media metrics within the existing reporting setup.
06. Outcome
The dedicated dashboard gives the team one place to review Google Ads performance across advertising, sales, and profitability metrics. It supports faster performance reviews and reduces the need to navigate separate views for each key indicator.
Page · Plain text
Smart AI Podcast Audio Script Generator from BBC News
To turn positive and interesting news stories into podcast-style audio scripts using AI.
Section: AI Agents
Project Overview
Category: AI Agents Technologies: n8n, BBC News, Google Gemini
This automation collects news articles from the BBC website, evaluates their suitability for podcast content, extracts the full article text, and uses AI to prepare scripts for audio conversion.
01. The Challenge
Manually finding interesting news, reviewing full articles, and rewriting them into conversational podcast scripts can be time-consuming. Not every news story is appropriate for an engaging podcast, so content must be screened before it moves forward.
02. The Solution
An n8n workflow automates the news-to-script preparation process. It retrieves BBC headlines, classifies stories using Google Gemini, extracts suitable articles, and transforms their content into friendly, podcast-style scripts.
03. How It Works
Step 1 — Fetch BBC News: Retrieve the BBC homepage and extract available news headlines and descriptions.
Step 2 — Process Headlines: Split the extracted articles into individual items and limit processing to 10 headlines.
Step 3 — Classify Stories: Use an AI news classifier to identify articles suitable for podcast content and separate unsuitable stories.
Step 4 — Extract Full Articles: Retrieve the full webpage content for stories that pass classification.
Step 5 — Filter and Generate Scripts: Process the article content and use an AI language model to rewrite suitable news into warm, clear, engaging podcast scripts.
Step 6 — Validate Output: Use structured output parsing and filtering to prepare the generated content for the next stage.
Step 7 — Prepare for Audio: Send suitable scripts to a Hugging Face API endpoint for the subsequent audio-generation stage.
04. Workflow
05. Key Features
- Automated BBC news collection
- AI-powered article suitability classification
- Full-article extraction for selected stories
- Conversational podcast script generation
- Structured output validation
- Integration with a Hugging Face API for the audio stage
06. Business Value
The workflow reduces manual research and rewriting, creates a repeatable news-to-script process, and helps prepare selected news stories for podcast production more efficiently.
07. Final Outcome
A reusable AI-powered pipeline that transforms BBC news articles into podcast-ready scripts, connecting news collection, AI classification, content extraction, script generation, and downstream audio processing in one workflow.
Page · Plain text
Shopify to Google Sheets Data Transfer with Task Allocation
Leveraged expertise in API integration and Google Sheets to create an automated system that transfers data from Shopify to Google Sheets using the ‘Sync With’ extension.
Section: Google Apps Script
Project Overview
This project uses Google Apps Script and Google Sheets to automate data transfer from Shopify and distribute customer-specific tasks across agents. The system uses the Sync With extension to transfer Shopify data to Google Sheets and integrates the resulting data with Aircall for customer outreach.
The system is configured to update daily.
Tools: Google Apps Script, Shopify, Google Sheets, and Aircall.
01. The Objective
The objective was to automate the transfer of Shopify data into Google Sheets and allocate customer-specific tasks to agents, reducing the need for manual task distribution.
02. The Solution
Google Apps Script functions handle the data processing and task allocation. The system uses the agent roster to distribute unattended calls evenly across available agents and integrates the data with Aircall for customer outreach.
03. How It Works
Step 1: Transfer Shopify Data
Shopify data is transferred to Google Sheets using the Sync With extension.
Step 2: Process the Agent Roster
Google Apps Script reads the agent names from the working sheet.
Step 3: Distribute Tasks
The task-distribution function calculates the allocation of data across the agent roster and assigns tasks evenly.
Step 4: Integrate with Aircall
The resulting data is integrated into Aircall to support customer outreach.
Step 5: Update Daily
The system is configured to update daily.
04. Task Distribution Logic
The Google Apps Script function distributes unattended calls across the agent roster. The provided code checks the agent list, reads the data count, calculates the number of tasks per agent, and assigns the calculated values in the working sheet.
Image: The task-distribution function that splits unattended calls evenly across the agent roster.
05. Workflow Overview
06. Tools and Integrations
- Shopify: Source of the data being transferred.
- Sync With extension: Supports the transfer of Shopify data to Google Sheets.
- Google Sheets: Stores the transferred data and supports task allocation.
- Google Apps Script: Processes the data and distributes tasks across the agent roster.
- Aircall: Supports customer outreach using the integrated data.
07. Outcome
The solution automates Shopify data transfer, distributes customer-specific tasks across agents, and integrates the data with Aircall. The system is configured for daily updates.
Page · Plain text
Meta Ads Agent
Before, someone had to open Meta Ads Manager and Shopify every morning and compare the numbers by hand. Now an agent does it overnight and posts a short briefing in Slack. It flags problems and suggests changes, and…
Section: Custom SaaS Platforms, AI Agents
Overview
Before, someone had to open Meta Ads Manager and Shopify every morning and compare the numbers by hand. Now an agent does it overnight and posts a short briefing in Slack. It flags problems and suggests changes, and nothing is changed in Meta without approval.
The Problem
An online store owner spends money on Meta ads every day, and the numbers rarely agree with the store. Meta says it drove one amount of sales. Shopify shows what was really ordered. A broken ad can keep spending for days before anyone notices, and each day of that is money gone. Checking every campaign by hand takes hours. So it gets skipped when the week gets busy.
How It Works
- Every morning at 8:00 AM, the agent pulls yesterday's ad numbers from Meta: spend, impressions, clicks, purchases and revenue, down to each ad.
- It pulls the same days' orders and revenue from Shopify.
- It saves both in a database.
- It compares the revenue Meta claims with the orders Shopify recorded, and flags any day where Meta claims more.
- It calculates ROAS, cost per purchase, CPM, CTR, frequency, and conversion rate, and checks the rules: wasted spend, weak ad sets, tired creative, and room to scale.
- Claude writes the briefing in plain English from those calculated numbers. Claude doesn't do the math.
- It posts a short digest in Slack with a link to the full report page.
- Every hour it checks the alert limits and messages Slack only when one is crossed.
- Suggested changes, such as pausing an ad set or changing a budget, wait for a person to approve them.
- Approved changes run within set limits: a maximum budget change, a daily action cap, and a cooldown. Each one is logged with its before and after state. A kill switch stops everything.
Tech Stack
| Tool | Job in this workflow |
|---|
| Meta Marketing API | Supplies ad numbers and carries out approved pauses and budget changes |
| Shopify Admin API | Supplies orders and revenue, the actual sales |
| PostgreSQL | Stores daily snapshots and the full action history |
| Python (FastAPI) | Runs the schedule, the rules, the report page and the control panel |
| Claude API | Writes the daily briefing from the calculated numbers |
| Slack | Delivers the daily digest and alerts |
| Railway | Keeps the agent running around the clock |
| GitHub | Holds the full source code |
The team keeps using Ads Manager and Shopify exactly as before. The only new thing to read is one Slack message each morning.
Page · Plain text
Looker Studio: Meta Ads Dashboard
A Looker Studio dashboard tracking Meta ad spend, clicks, impressions and campaign-level ROAS in one live view.
Section: Looker Studio
01. Project Overview
This dashboard provides a consolidated overview of Meta Ads performance, combining campaign metrics with a detailed breakdown of individual ads. It helps users review traffic, advertising spend, impressions, and return on ad spend within a single reporting interface.
Paid Media Reporting
Built in Looker Studio to track Meta ad spend, clicks and campaign performance in one place, replacing manual exports from Meta Ads Manager.
- 21,767: Clicks
- 627,879: Impressions
- $35.2K: Spend
- 3.47%: CTR (all)
02. The Challenge
Reviewing advertising performance across multiple campaigns and ads can require switching between different views and manually comparing metrics. Without a consolidated report, it can be harder to identify how individual campaigns are performing and how advertising spend is distributed.
03. The Solution
A Looker Studio dashboard was created with two main reporting views:
- Performance Overview: Displays high-level metrics such as clicks, link clicks, impressions, ROAS, spend, and CTR.
- Campaign-Level Breakdown: Presents campaign and ad-level data, including ROAS, clicks, amount spent, impressions, and CPM.
- Date Range Selection: Allows users to review performance for a selected reporting period.
- Campaign Filtering: Supports filtering the detailed table by campaign name.
04. Dashboard One: Performance Overview
The overview page brings key advertising metrics together for a quick assessment of campaign activity.
Metrics shown in the supplied screenshot:
These values reflect the dashboard screenshot and should be interpreted according to the report's metric definitions and selected date range.
Image: Meta Ads dashboard overview: clicks, link clicks, impressions, ROAS and spend for a single brand’s campaigns.
05. Dashboard Two: Campaign-Level Analysis
The detailed reporting table provides a closer look at individual campaigns and ads. Users can compare performance indicators across rows and filter the table by campaign name.
The table includes:
Image: Campaign-level breakdown: ROAS, clicks, spend, impressions and CPM for every ad and campaign, filterable by name.
This view complements the overview by making individual campaign and ad performance easier to inspect.
06. Technology and Integration
- Looker Studio: Reporting, visualisation, and interactive filtering.
- Meta Ads: Advertising performance data.
07. Outcome
The dashboard consolidates Meta advertising metrics into a single reporting interface. The overview supports quick performance reviews, while the detailed table enables campaign-level comparisons without relying solely on separate manual exports.
Page · Plain text
Fulfilled Order Integration with ClickUp
This Make scenario is implemented so that whenever an order is fulfilled in Shopify, the order details are added to ClickUp.
Section: Make Automations
Project Overview
This Make automation connects Shopify with ClickUp, Google Sheets, and Slack to process fulfilled orders and update the relevant records.
When an order is fulfilled in Shopify, the scenario retrieves the order details, searches for a matching record in the Data Store, adds a row to Google Sheets, and updates a ClickUp task with custom fields. The workflow also includes Data Store and Slack actions after the ClickUp update.
The Solution
The Make scenario automates the order-fulfilment process by connecting the relevant applications in a single workflow.
- Shopify: Triggers the scenario when a new order is fulfilled and retrieves the order details.
- Data Store: Searches for a matching record using the available order information.
- Google Sheets: Adds a row containing the order information.
- ClickUp: Updates a task with custom fields using the processed order details.
- Data Store: Performs a follow-up action to delete a record.
- Slack: Creates a message as part of the workflow.
How It Works
1. Shopify Order Trigger
The workflow starts when Shopify detects a newly fulfilled order. This event initiates the scenario and provides the order information for subsequent steps.
2. Retrieve Order Details
The scenario retrieves the corresponding order details from Shopify so they can be used by the following modules.
3. Search the Data Store
The workflow searches the Data Store for a record associated with the order. This step helps the scenario use the available stored information before continuing.
4. Add a Row to Google Sheets
The order information is added to Google Sheets, creating a record of the fulfilled order in the spreadsheet.
5. Update the ClickUp Task
The scenario updates a ClickUp task using custom fields. This connects the order-processing workflow with task management.
6. Perform Follow-up Actions
After the ClickUp update, the scenario branches into two actions: deleting a record from the Data Store and creating a message in Slack.
Image: Screenshot of working automation of make.com
Workflow Architecture
Tools and Integrations
- Make: Connects the applications and orchestrates the automation.
- Shopify: Supplies the order event and order details.
- Data Store: Searches and deletes records.
- Google Sheets: Stores order information in a spreadsheet.
- ClickUp: Updates tasks with custom fields.
- Slack: Creates a message through the workflow.
Outcome
The scenario connects Shopify order fulfilment with spreadsheet recordkeeping, ClickUp task updates, Data Store operations, and Slack messaging. It brings these actions together in one Make automation, reducing the need to perform each connected step manually.
Page · Plain text
Python MCP Server Connecting Claude to a Field-Service CRM
A hosted, OAuth-protected MCP server in Python that lets a home-services business ask Claude about customers, jobs, invoices and leads, with write actions hidden unless allowed.
Section: Python Automation
Project Overview
This project connects Claude to Housecall Pro, enabling a home-services business to ask questions about customers, jobs, invoices, and leads through an MCP server built with Python and FastMCP.
Technology: Python, FastMCP, OAuth 2.0, REST API, Railway, Claude
01. The Problem
The business wanted to interact with its field-service data through Claude and perform permitted actions without giving the AI direct access to the raw database.
02. The Solution
A Python MCP server was developed to expose the Housecall Pro REST API through approximately 20 domain modules, covering customers, jobs, estimates, invoices, leads, employees, scheduling, webhooks, and more.
The server is hosted on Railway and connects to claude.ai.
03. Key Features
- OAuth 2.0 Authentication: Uses GitHub as the OAuth provider, with authentication redirecting back to claude.ai.
- Domain-Specific Tools: Organizes tools into namespaces such as
customers_*, jobs_*, and invoices_*. - Read-Only Enforcement: Middleware hides tools containing
create, update, delete, send, void, or dispatch in their names unless explicitly allowed. - REST API Integration: Exposes field-service functionality through a unified FastMCP application.
- Hosted Deployment: Runs on Railway for connection to Claude.
04. How It Works
- The user authenticates through the OAuth login flow.
- Claude connects to the hosted MCP server.
- FastMCP exposes the available CRM tools through domain-specific modules.
- Permission middleware determines which tools are visible to the agent.
- Claude uses the available tools to interact with the field-service CRM API.
Image: The server entry point: GitHub OAuth in front, one FastMCP app, and each domain module (customers, jobs, estimates, invoices, leads, employees) mounted under its own namespace.
05. Workflow
06. Implementation
The server entry point mounts the CRM domain modules under one FastMCP application. Each module handles a specific area of the field-service API, while OAuth authentication and permission middleware control access to the available tools.
Image: The repository: one Python module for each area of the field-service API, plus a Procfile for deployment on Railway. The commit messages are blurred.
The repository contains separate Python modules for the different API domains and a Procfile for Railway deployment.
07. Outcome
The solution provides Claude with a structured interface to field-service CRM data, with OAuth authentication, domain-specific tool namespaces, and protocol-level controls over which actions are exposed to each agent.
Built with
Python, FastMCP, OAuth 2.0, REST and Railway.
Page · Plain text
Automated Column Management in Inventory Sheet
Developed an app script to automatically update columns in an inventory sheet based on values in another sheet, enabling seamless data synchronization within Google Sheets.
Section: Google Apps Script
Automated Column Management in Inventory Sheet
Automating inventory column updates and synchronizing information between Google Sheets using Google Apps Script.
Project Overview
This project uses Google Apps Script to update columns in an inventory sheet based on values in another spreadsheet. It also provides custom menu options for updating inventory values and adding leading zeros.
Tools: Google Apps Script, Google Sheets.
01. The Challenge
Maintaining inventory information across linked spreadsheets requires consistent updates. Manual changes can leave records out of sync, while inventory values such as SKU and location codes may require leading zeros to be preserved.
02. The Solution
A Google Apps Script solution was developed to automate inventory updates and synchronize relevant column values between spreadsheets.
The scripts provide custom menu actions to run inventory updates and normalize leading zeros when needed.
03. How It Works
- Read spreadsheet data: The script accesses the main spreadsheet and relevant inventory sheets.
- Compare records: It reads client information and account status values to identify the records that need processing.
- Update inventory columns: The script updates inventory-related values based on the information in the linked spreadsheet.
- Run custom actions: Users can select options from the Google Sheets custom menu to update inventories or add leading zeros.
04. Workflow Architecture
The workflow connects the main spreadsheet, Google Apps Script, and the linked inventory spreadsheet.
Custom Menu Actions
The provided Apps Script screenshots show these menu options:
- Update Inventories — runs the inventory update function.
- Add Leading Zeros — runs the function for adding leading zeros.
05. Implementation Screenshots
Inventory synchronization
The first screenshot shows the Apps Script function for checking account status and synchronizing information between the main sheet and a linked inventory spreadsheet.
Image: Syncing active/inactive status between a main sheet and a linked inventory spreadsheet.
Custom inventory menu
The second screenshot shows the custom menu available in Google Sheets for running inventory updates and adding leading zeros.
Image: A custom menu for updating inventory values and normalizing leading zeros on demand.
06. Tools and Integrations
- Google Apps Script: Executes the inventory update and leading-zero functions.
- Google Sheets: Stores inventory records and provides the interface for running custom menu actions.
07. Outcome
The solution automates inventory column updates between linked spreadsheets and provides on-demand menu actions for inventory updates and leading-zero normalization.
Page · Plain text
AI-Powered Social Post Generator: From Spreadsheet to Socials in Seconds!
Automatically create short, engaging, and fact-based posts (with emojis!) based on your content ideas, and publish them to the right platform.
Section: AI Agents
AI-Powered Social Post Generator
Automatically turn content ideas in Google Sheets into engaging, platform-specific social media posts using Google Gemini, with publishing routed to LinkedIn or X.
Category: AI Agents Tools: Google Sheets, Google Gemini, LinkedIn, X (Twitter)
1. Project Overview
This workflow automates social media content creation and publishing. It reads content ideas and the selected platform from Google Sheets, uses Google Gemini to generate a short, fact-based post, and routes the result to the appropriate social network.
2. The Challenge
Creating and publishing social media content manually involves several repetitive steps:
- Reviewing content ideas in a spreadsheet.
- Writing posts suitable for each social platform.
- Checking which ideas have already been published.
- Copying and pasting content into the correct platform.
- Keeping track of publishing status.
These tasks can slow down content production and create unnecessary manual work.
3. The Solution
An AI-powered workflow connects Google Sheets with Google Gemini and social media publishing tools.
The workflow starts manually when the user clicks Test workflow. It reads the spreadsheet, checks publication status, generates content with Gemini, and uses conditional logic to route the post to LinkedIn or X according to the selected platform.
4. How the Workflow Works
Image: n8n workflow
- Manual Trigger: The user starts the workflow with a click.
- Read Google Sheets: Retrieve content ideas and their target platforms.
- Check Publishing Status: Select ideas marked
0, indicating they have not yet been published. - Generate Social Content: Google Gemini creates a concise, fact-based post with suitable emojis.
- Route by Platform: Conditional branches determine whether the post should go to LinkedIn or X.
- Publish the Post: The appropriate platform integration handles publishing.
5. Workflow
6. Key Features
- Spreadsheet-Driven Content: Manage content ideas and platform choices in one place.
- AI-Assisted Writing: Generate concise, engaging posts with Google Gemini.
- Publication Status Filtering: Avoid selecting ideas already marked as published.
- Platform-Based Routing: Send content to LinkedIn or X based on the selected destination.
- One-Click Execution: Start the workflow manually when content is ready.
7. Business Value
The workflow reduces repetitive writing and publishing tasks, makes content production more organized, and simplifies the process of turning spreadsheet ideas into social media posts.
8. Final Outcome
A streamlined content workflow that connects Google Sheets, Google Gemini, and social media publishing integrations—helping users move from a content idea to a platform-specific post with less manual effort.
Page · Plain text
Monday.com Workflow Synchronization
A centralized dashboard for managing one-way and two-way synchronization across Monday.com boards
Section: Python Automation
Overview
The platform synchronizes project and deal information from the PM board to Media Buyer and Account Strategist boards, while keeping the Master CRM and individual closer boards aligned through separate two-way workflows. Each workflow maintains its own configuration, field mappings, and execution logs.
The Problem
Teams working across multiple Monday.com boards may need to repeat updates manually. This can leave records inconsistent and makes it harder to manage changes from both sides, prevent repeated updates, and identify synchronization errors or skipped records.
How It Works
- Identify records: The workflow checks configured Monday.com boards through automatic polling or a supported manual run.
- Match destination items: Board relationships, role mappings, and linked item identifiers are used to find the corresponding record.
- Apply field mappings: Configured rules determine which fields are synchronized and in which direction.
- Create or update records: Missing items are created where configured; existing matching items are updated.
- Apply safeguards: Two-way workflows use conflict policies and loop-prevention rules to avoid repeatedly processing their own updates.
- Record the outcome: Each workflow logs successful updates, skipped records, errors, and execution detail.
The Result
The platform brings multiple board synchronization workflows into one dashboard. Teams can keep configured records aligned, manage one-way and two-way updates separately, and review execution logs to understand what was synchronized, skipped, or unsuccessful.
Results & Performance Metrics
| Metric | Observed Result |
|---|
| Records synchronized | 295 |
| Errors encountered | 4 |
| Records skipped | 2 |
| Records dropped | 0 |
| Monitoring availability | 24/7 |
| Synchronization interval | 18 seconds |
Tech Stack
- Python: Core application and synchronization logic.
- Flask: Web application and dashboard backend.
- SQLite: Stores synchronization state and execution records.
- Monday.com API / Monday SDK: Accesses board data and applies updates.
- HTML, CSS and JavaScript: Provide the dashboard interface and frontend interactions.
Where This Pattern Applies
This solution helps businesses keep information consistent across multiple Monday.com boards and teams.
The same approach can be used in:
- Sales & CRM: Synchronize client records, deals, and ownership.
- Project Management: Keep project details, deadlines, and statuses aligned.
- Media Buying: Share campaign and client information across teams.
- Account Management: Maintain consistent client records and responsibilities.
- Marketing: Coordinate campaigns and team activities.
- Business Operations: Synchronize operational records across departments.
The underlying pattern remains the same: identify matching records, apply configured field mappings, create or update items, handle conflicting changes, and log synchronization results.
Page · Plain text
End of part 1 of 7. Continue with part 2.