How to Insert a Current Timestamp in Any Zapier Step Using Zap Meta

A practical field guide from Automation Ace.

How to Insert a Current Timestamp in Any Zapier Step Using Zap Meta

Every Zapier action step's field mapper includes a special set of values under the "Zap Meta" section — built-in fields that Zapier populates at run time with information about the current Zap execution. The most useful of these for everyday automation is human_now: a human-readable timestamp of the current date and time at the moment the Zap runs. You can map it directly into any field that accepts text — date fields, note fields, log columns, record names — without adding any extra steps.

Where to Find Zap Meta Fields

In any action step's field mapper, click into a field and open the data picker. Scroll to the bottom of the list — below all your trigger and previous step outputs — to find the Zap Meta section. It contains a fixed set of values that Zapier provides for every run.

The Zap Meta Fields

The available Zap Meta fields (names may vary slightly by Zapier version):

• human_now — the current date and time in a human-readable format, e.g. June 29, 2025 at 02:34PM
• machine_now — the current date and time in ISO 8601 format, e.g. 2025-06-29T14:34:00Z — useful for date fields that expect a parseable timestamp
• zap_id — the numeric ID of the Zap
• zap_name — the name of the Zap as set in the Zap editor
• bundle_id — a unique identifier for the specific Zap run
• step_id — the ID of the current step in the Zap

human_now and machine_now are the fields used in practice. The others are useful for debugging and logging.

Common Uses for human_now

• Timestamping records: Add a "Created via Zap at [time]" note to every record created by a Zap, mapped to a notes or description field
• Log entries: Stamp each row written to a Google Sheet with the time it was added
• Audit fields: Populate a "Last Updated" or "Processed At" field in Airtable, Notion, or a CRM
• Notification messages: Include the current time in a Slack message or email body: New lead received at {{human_now}}
• Deduplication: Use machine_now as a unique value in a webhook payload to prevent Zapier from deduplicating repeated requests — see webhook trigger deduplication

human_now vs. machine_now: Which to Use

human_now is for text fields where a person will read the value — a note, a label, a message body. The format is readable but not parseable by most date-aware systems.

machine_now is for date/time fields in apps that expect an ISO 8601 timestamp — Airtable date fields, Google Sheets date columns, HubSpot date properties. Most apps parse ISO format correctly. Use machine_now when the receiving app needs to sort, filter, or calculate based on the timestamp.

Timezone Behavior

Zap Meta timestamps use UTC by default. human_now displays the time in UTC, not your local timezone or the account's timezone setting. If you need a timezone-adjusted timestamp in a specific format, use a Code step instead:

// Code step: current time in a specific timezone
const now = new Date();
const parts = new Intl.DateTimeFormat('en-US', {
  timeZone: 'America/Chicago',
  year: 'numeric', month: '2-digit', day: '2-digit',
  hour: '2-digit', minute: '2-digit', second: '2-digit',
  hour12: true
}).formatToParts(now);

const get = (type) => parts.find(p => p.type === type)?.value || '';
const formatted = `${get('month')}/${get('day')}/${get('year')} ${get('hour')}:${get('minute')} ${get('dayPeriod')} CT`;

output = {
  timestamp_local: formatted,
  timestamp_iso: now.toISOString()
};

For business-hours filtering and timezone-aware scheduling patterns, see running Zaps during business hours only.

Using Zap Meta for Logging and Audit Trails

A practical pattern: every time a Zap creates or updates a record, also write a log entry to a Google Sheet or Airtable table. The log row includes:

• human_now — when the Zap ran
• zap_name — which Zap produced this entry
• bundle_id — the unique run ID (useful for debugging a specific run)
• Any key field from the trigger — the record ID, email, or order number being processed

This creates a lightweight audit trail without any custom code — just map Zap Meta fields directly into a "Create Row" action alongside your regular trigger data.

Zap Meta vs. Trigger Timestamp

Many triggers include a timestamp from the source system — a form submission time, an order created_at date, a webhook received_at field. That timestamp reflects when the event happened in the source app. machine_now / human_now reflect when the Zap step ran, which may be seconds or minutes later (due to polling intervals, queue delays, etc.).

Use the trigger's timestamp when you care about when the event originated. Use Zap Meta timestamps when you care about when the Zap processed it — for audit logs, "processed at" fields, and deduplication keys.

Zap Meta fields are available in every Zap step's field mapper with no configuration — scroll to the bottom of the data picker to find them. human_now is the simplest way to stamp any record with the current time. machine_now works for date fields that need a parseable ISO timestamp. For timezone-adjusted or custom-formatted timestamps, a Code step with Intl.DateTimeFormat gives full control.

For timezone-aware timestamp formatting in a Code step, see parsing timestamps into parts in Zapier Code steps. For using a timestamp to prevent webhook deduplication, see webhook trigger deduplication in Zapier. For setting default values when fields are empty, see default values with Zapier Formatter. For help with timestamps or logging in your Zap, talk to Automation Ace.