Overview
You can generate a Discord-compatible timestamp in Zapier using the Formatter app's Date / Time > Format transform or our built-in System variables feature. Discord uses unix timestamps wrapped in a special syntax to display times that automatically adjust to each viewer's local timezone. Zapier's Formatter can convert any date value in your Zap into the unix number Discord needs.
Step-by-step guide
Method 1: Convert a date from a previous step to a Discord timestamp
- Add a Formatter step to your Zap. In the Zap editor, click the + icon to add a new action. Search for and select Formatter by Zapier.
- Select Date / Time as the action event. Click the Action event dropdown and choose Date / Time, then click Continue.
- Choose Format in the Transform field. Then, in the To Format field, select the X option. This outputs a plain unix number in seconds.
- Map your date field to the Input. In the Input field, map the date value from your trigger or a previous step. This could be a meeting start time, a scheduled event date, a form submission timestamp, or any other date field.
- Test the step. Click Test step, which will output a unix timestamp number like 1776697200.
- Wrap the unix number in Discord's timestamp syntax. In your Discord action step (for example, Send Channel Message), build your message text by typing the opening syntax, then mapping the Formatter output, then closing it. For example <t:1776697200> would output it in the default date and time (e.g. April 20, 2026 3:00 PM).
Method 2: Use the current time as a Discord timestamp
- Select the system variable in Unix format from the library. In the bottom left on the Zap editor, click on the Library button. Next click on Variables, then click the System tab. Next click on the variable named Current time (UNIX), this will copy the variable to your clipboard. You can then close the library and paste the system variable into the Message Text field. This inserts the exact time the Zap runs as a Unix timestamp.
- Wrap the system variable in Discord's timestamp syntax. The output will be the unix timestamp for the moment your Zap runs. Wrap it like <t:SYSTEM_VARIABLE:t> in your Discord message to show only the time (e.g. 3:00 PM).
Discord timestamp format options
Once you have your unix number, you can use any of these Discord timestamp formats in your message field:
| Syntax | Format |
|---|---|
| <t:UNIXTIMESTAMP> | Default date and time (e.g. April 20, 2026 3:00 PM) |
| <t:UNIXTIMESTAMP:R> | Relative time (e.g. 3 days ago) |
| <t:UNIXTIMESTAMP:d> | Short date (e.g. 20/04/2025) |
| <t:UNIXTIMESTAMP:D> | Long date (e.g. April 20, 2026) |
| <t:UNIXTIMESTAMP:t> | Short time (e.g. 3:00 PM) |
| <t:UNIXTIMESTAMP:T> | Long time (e.g. 3:00:00 PM) |
| <t:UNIXTIMESTAMP:f> | Short date and time (e.g. April 20, 2026 at 3:00 PM) |
| <t:UNIXTIMESTAMP:F> | Long date and time (e.g. Monday, April 20, 2026 3:00 PM) |
Replace UNIXTIMESTAMP with the mapped output from your Formatter step in each case.
Key notes and limitations
- Discord timestamps always display in the viewer's own local timezone. You do not need to set a timezone in the Formatter step as the unix number is timezone-neutral, and Discord handles the conversion for each viewer.
- Formatter actions require a paid Zapier plan, however they do not count towards your Task usage.
- The unix timestamp Formatter outputs is in seconds. Some tools and code steps output milliseconds (a 13-digit number). If your timestamp looks wrong in Discord, divide it by 1000 using a Formatter (Numbers) action step.
- The <t:UNIX> syntax only works in Discord message text fields. It does not render in channel names, or other non-message areas.
Frequently asked questions
Q: How do I make a Discord timestamp that shows in everyone's local timezone?
A: All Discord timestamps automatically display in the viewer's timezone. You just need to format your date as a unix timestamp using Formatter and wrap it in <t:UNIXTIMESTAMP> as Discord handles the timezone conversion for every viewer automatically.
Q: How do I make a relative timestamp in Discord?
Use <t:UNIXTIMESTAMP:R> in your message, where UNIX is the unix timestamp from your Formatter step. Discord will display it as "yesterday" or "X days ago" relative to when the message is read.
Q: Why is my Discord timestamp showing the wrong time?
A: The most common cause is a timezone mismatch. If your source date does not include timezone info, Zapier assumes UTC. Set the From Timezone field in your Formatter step to match your source date's timezone.