Weekly Warmly account log to Google Sheets

By General Input

Every Monday morning, append last week's warm accounts from Warmly to a Google Sheet so revops has a clean longitudinal log.

Integrations

  • Warmly
  • Google Sheets

Type

Deterministic Code

Categories

  • Sales
  • Operations

Build a code workflow that runs every Monday at 7am America/New_York and logs the prior seven days of warm accounts from Warmly into a Google Sheet, one row per account. This is a deterministic ETL: list, transform, append. No judgement steps, no LLM nodes.

Trigger: cron, every Monday at 07:00 America/New_York.

Install-time inputs that the installer fills in once: the destination Google Sheet (spreadsheet id or URL) and the tab name to append to. Assume the tab already exists with a header row.

Step 1. Page through Warmly list_warm_accounts for the prior 7 days. Use take=500 and offset starting at 0. After each page, advance offset by take and stop when the returned array length is less than take. Collect all accounts into a single array. Scope the time window to the last 7 days ending at the run start. Reference the Warmly common_docs (call get_service for warmly) for the agent-tools execute gateway shape and pagination rules.

Step 2. For each account, build a row with these columns in this order: account name, domain, total sessions, distinct identified visitors, distinct pages visited, top page viewed, first-seen timestamp (ISO 8601), last-seen timestamp (ISO 8601), CRM intersection field (the Warmly indicator of whether the account is already in the connected CRM).

Step 3. Append the rows to the configured Google Sheet tab using Append Values with valueInputOption=USER_ENTERED so dates render naturally. Send the rows in a single batch where possible. If there are zero accounts for the week, write nothing and exit cleanly.

Error handling: if Warmly returns 429, back off ~60 seconds and retry the same page. If Google Sheets returns 429 or 503, retry the append with exponential backoff (start 1s, cap 64s, add jitter). Surface a clear failure if the configured tab does not exist.

The same tab should grow week over week as a longitudinal record of warm-account intent. Do not deduplicate against prior weeks. Each Monday adds one batch of fresh rows for the trailing seven days.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentLocal listing health board for every location you manageLet support send one-off Loops emails without an engineerStop cold emails to anyone with a live deal in PipedriveiMessage campaign console with pre-flight checks and delivery boardLinkedIn Ads budget pacing dashboard for every client accountFront desk appointment confirmation board for the next 3 daysGive your team Looker numbers without buying more seatsBuild audience segments from product usage and push to LoopsTurn the people who engage with your posts into Pipedrive leads