> For clean Markdown content of this page, append .md to this URL. For the complete documentation index, see https://learning.postman.com/llms.txt. # The Request block The **Request** block is one type of trigger block required to create a [deployable flow](/flows/reference/flows-actions-overview/) that runs in the Postman cloud. The **Request** block takes request data sent to a flow's URL and routes the data through its **Headers**, **Params**, and **Body** output ports. The only way to add a **Request** block to a flow is to change the [**Start** block's](/flows/reference/blocks/start/) trigger to **Request**. The **Request** block can't be deleted. Prior to a flow being deployed to the cloud, the **Request** block gets values for headers, parameters, and the request body from [scenarios](/flows/build-flows/configure/scenarios/). By running different scenarios, you can test how your flow will behave once it's running in the cloud. Testing with scenarios is necessary because the flow won't have a URL until you deploy it to the cloud. The **Request** block can ingest input data of up to 5 megabytes if you're on a [paid Postman plan](https://www.postman.com/pricing/), or 1 megabyte if you're on the Postman Free plan. ## Outputs * **Headers** - Sends the request headers. * **Params** - Sends the request's query parameters. * **Body** - Sends the request body. ## Supported request formats Flows deployed in the cloud accept requests using any HTTP method supported by Postman. You can pass data to deployed flows in any format Postman supports, including JSON bodies, URL-encoded data, and form data. No specific request headers are required. ## Setup To add a **Request** block to a flow, click **Change trigger** on the [**Start**](/flows/reference/blocks/start/), [**Schedule**](/flows/reference/blocks/schedule/), or [**MCP**](/flows/reference/blocks/mcp/) block and select API icon **Request**.