Every Monday, log last week's Dialpad calls to Sheets

By General Input

Every Monday morning, flatten the previous week of Dialpad calls into a Google Sheet so your ops team can pivot on volume, duration, and rep activity.

Integrations

  • Dialpad
  • Google Sheets

Type

Deterministic Code

Categories

  • Operations
  • Sales

Every Monday at 8am, log the previous week's Dialpad calls into a Google Sheet so ops can pivot on the data.

Use Dialpad List Calls with a 7-day time range (the previous Monday 00:00 through the following Sunday 23:59:59 in the user's chosen timezone) to pull every call. Then use Google Sheets Append Values on the user-selected spreadsheet and worksheet to add one row per call with a fixed column layout: date, direction, from number, to number, internal user (rep), duration in minutes, call state (completed / missed / voicemail), whether it was recorded, and the Dialpad call id for drill-down.

Dialpad returns durations in milliseconds and timestamps in Unix epoch millis, so convert duration to minutes (rounded to one decimal) and format each timestamp as a human-readable date string in the user's chosen timezone before appending. Represent booleans (recorded yes/no) as plain TRUE / FALSE strings and keep phone numbers in their E.164 form so they stay pivotable.

Paginate through Dialpad's List Calls response (follow the cursor) so every call in the seven-day window is included, then build one batch of rows and send them to Google Sheets Append Values in a single call to stay well under the 2 MB payload guidance.

Let the user pick the target spreadsheet and worksheet, the timezone used for the date column, and a toggle for whether to include internal-to-internal calls (calls where both the caller and callee are Dialpad users in the same company). When that toggle is off, filter those calls out before appending so the log only reflects real customer conversations.

This is a code workflow because it's a straight flatten-and-append with no reasoning step: every call becomes exactly one row, the column layout is fixed, and there are no judgement calls between fetch and write.

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