Resource parameter types

There are 3 types of resource parameters.

resource_file_<parameter_name> and resource_directory_<parameter_name>

Use these parameters if the artifact needs a file or multiple files in a single directory to be executed.

If you run the artifact requiring multiple resource files in Talend Studio, you need to provide the path to the folder where they are located as the value of the resource_directory_<parameter_name> parameter.

If you are running the task based on the artifact requiring multiple resource files, you must create the resource in Talend Management Console after the artifact is published from Talend Studio to Talend Cloud. The resource files must be compressed to a single file, which must be uploaded in Talend Management Console as a Directory-type resource. The directory path is extracted during the task execution.

resource_flow_temp_folder

Use this parameter if you are executing a task in Talend Management Console and need to define a specific temporary folder for the task to use during execution. The temporary folder is created before the task is triggered and it is available to all actions in the task. The folder is deleted after the task is executed.

You must set the parameter type to String.

resource_webhook_payload

Use this context parameter to receive data from the source system when the task (artifact) execution is configured to be triggered via a webhook. The external system will call the task and pass data to this parameter.

Webhooks must be defined in a JSON format, where:

type: media type of the payload taken from Content-Type header, for example, application/json;charset=utf-8.
data: payload data

The following payload types are supported:

application/xml
application/json
text/plain
text/xml
Calls to the webhook endpoint with an empty payload are valid and supported.

Example:

[ { "type": "text/plain;charset=UTF-8", "data": "Some Data" }, { "type": "application/xml", "data": "<SomeXml/>" } ]

The example above does not show the original structure of the request sent to the webhook. Instead, it illustrates the schema to which Talend Management Console converts the incoming data, as the resource_webhook_payload variable requires this format.

Important: Special response cases:

Salesforce: Calls with Salesforce-specific payloads (for example, containing the soap.sforce.com references) respond with 200 OK instead of 204 No Content, even when the response body is empty.

Dropbox: When the DropboxWebhooks/1.0 user-agent header is included in the request, the webhook responds with 200 OK and includes the value of the challenge parameter in the response body. For example, for a call similar to this one:
```
GET https://webhooks.eu.cloud.talend.com/mywebhook/11fe60a514414a2a8b938b29084c4a29?challenge=parameter
User-Agent: DropboxWebhooks/1.0
```
The response body looks like:
```
Response:
           parameter
           Content-Type: text/plain;charset=UTF-8
           Content-Length: 9
```

You must set the parameter type to String.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here