> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/automation-flows/all-components/data-transformation/timer.md).

# Timer

### Overview

The **Timer Component** (identified in the interface by the descriptive technical name `timer`) is a utility node focused on time-based flow control. Its main function is to apply a scheduled pause in the automation execution, holding the contact at that exact stage of the journey for a set period before releasing it to the next connected block. It is essential for humanizing interactions, simulating typing, and structuring spaced relationship cadences.

### Configuration Parameters

The block's parameterization manages the engine's waiting window through a single input criterion:

* **Timeout:** Numeric input field where the administrator enters the desired retention interval. The platform's execution engine interprets the entered value **strictly in seconds** (e.g., to configure a 1-minute pause, you must enter the value of `60`).<br>

### Visual Builder

The graphical interface values operational minimalism to act cleanly as a waiting queue processing node:

* **Direct Input Panel:** Displays a streamlined layout composed solely of the timeout entry field. As it is a purely logical component internal to the system core, it does not require selectors for credentials, media, or mapping variables.<br>
* **Continuous Connection Port:** In the flow design editor, the block presents a traditional input port and a single physical output port. There are no complex branches; the contact enters, waits for the programmed time to elapse, and then continues linearly through the output connector.<br>

### Special Operators

The logical properties of this component manage asynchronous timers and background job scheduling (*background job scheduling*):

* **Sleep-State Queuing:** When passing through this component, the automation engine pauses reading the script for that specific contact, saving the current state of the journey and creating an internal asynchronous schedule.<br>
* **Execution Based on Fixed Time Unit:** The field interpreter does not accept text strings, complex mathematical operators, or time formats (such as "00:05:00"). It requires a simple integer representing the raw time calculated in seconds.<br>

### Practical Examples

The table below demonstrates scenarios and mathematical equivalents for programming efficient pauses within the automation tree:

| **Configured Timeout** | **Real-Time Equivalent** | **System Behavior**                                     | **Practical Use Case**                                                                                                                                                            |
| ---------------------- | ------------------------ | ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `5`                    | 5 seconds                | Holds the flow for 5 seconds before advancing.          | **Typing Simulation:** Used between two consecutive text message blocks to simulate a human operator typing, avoiding the instant sending of dense text blocks.                   |
| `300`                  | 5 minutes                | Keeps the contact in the queue for exactly 5 minutes.   | **Response Interval:** Wait a short period after a user action (such as filling out a form on the website) before sending a follow-up or check-in message.                        |
| `3600`                 | 1 hour                   | Holds execution for 1 hour before releasing the output. | **Spaced Relationship Cadence:** After sending rich content or an email, the system waits one hour before making a new active feedback contact with the customer on the platform. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hablla.com/hablla-docs-en/automation-flows/all-components/data-transformation/timer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.