# Components ## Communication For more information, see the [communication documentation](https://developers.make.com/custom-apps-documentation/component-blocks/api). * The communication `response` is extended with the `wrapper` object. * `limit` is not available in `response` as the result of the action should always be only one bundle * Communication can be [request-less](https://developers.make.com/custom-apps-documentation/component-blocks/api/request-less-communication). ### Static parameters You can use [static parameters](https://developers.make.com/custom-apps-documentation/component-blocks/parameters) inside the action module without any restrictions. ### Mappable parameters You can use [mappable parameters](https://developers.make.com/custom-apps-documentation/component-blocks/mappable-parameters) inside the action module without any restrictions. ### Interface The action module should always [output only one bundle](https://developers.make.com/custom-apps-documentation/component-blocks/interface). ### Samples To help the users with setting up your module, you can provide [samples](https://developers.make.com/custom-apps-documentation/component-blocks/samples). ### Scope When using an OAuth type of connection, use the [scope](https://developers.make.com/custom-apps-documentation/component-blocks/scope) to define scopes required by this action. ### Available IML variables These IML variables are available for you to use everywhere in this module:

Variable	Description
`now`	Current date and time
`environment`	TBD
`temp`	Contains custom variables created via the `temp` directive.
`parameters`	Contains the module’s input parameters.
`connection`	Contains the connection’s data collection.
`common`	Contains the app’s common data collection.
`data`	Contains the module’s data collection.
`scenario`	TBD
`metadata.expect`	Contains the module’s raw parameters array in the way you have specified it in the configuration.
`metadata.interface`	Contains module’s raw interface array in the way you have specified it in the configuration.

Additional variables available for the response object:

Variable	Description
`output`	When using the `wrapper` directive, the `output` variable represents the result of the `output`directive.

Additional variables available after using the `iterate` directive, i.e. in `wrapper` or `pagination` directives:

Variable	Description
`iterate.container.first`	Represents the first item of the array you iterated.
`iterate.container.last`	Represents the last item of the array you iterated.

Additional variables available for pagination and response objects:

Variable	Description
`body`	Contains the body that was retrieved from the last request.
`headers`	Contains the response headers that were retrieved from the last request.
`items`	When iterating this variable represents the current item that is being iterated.

## Action module example {% tabs %} {% tab title="Appearance" %}

{% endtab %} {% tab title="Communication" %} ```json { "url": "/api/users/create", "body": { "name": "{{parameters.name}}", "email": "{{lower(parameters.email)}}" }, "method": "POST", "response": { "output": { "id": "{{body.id}}" } } } ``` {% endtab %} {% tab title="Static parameters" %} ```json [] ``` {% endtab %} {% tab title="Mappable parameters" %} ```json [ { "name": "email", "type": "email", "label": "Email address", "required": true }, { "name": "name", "type": "text", "label": "Name", "required": true } ] ``` {% endtab %} {% tab title="Interface" %} ```json [ { "name": "id", "type": "uinteger", "label": "User ID" } ] ``` {% endtab %} {% tab title="Samples" %} ```json { "id": 1 } ``` {% endtab %} {% endtabs %}