[APP] Talend

[mroy-seedbox]

Name of app / service Talend

Link to developer documentation

• API Documentation
• API Portal

Is lack of support preventing you from building workflows, or do you have a workaround? We are not blocked. We can use environment variables to hold the credentials.

Are there specific actions, or triggers, you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each! No specific actions required at this time (we can handle that with code steps). It would just be nice to have an app to store the credentials, like you have for Databricks & DBT (even though there are no actions or triggers).

[mroy-seedbox]

If a basic app can be created for this, we'd love to contribute some components to it! ❤️

[dannyroosevelt]

@mroy-seedbox we'll get right on it! By the way, can you let us know what triggers or actions you'd like to see for Databricks, so we can get some published?

[mroy-seedbox]

We're working on some Databricks components right now!

The main actions that we care about right now are:

• Jobs: Run now
• Jobs: Get run
• Jobs: Get run output

[sergio-eliot-rodriguez]

notes on outreach: applied for partnerships, copied integrations@pd

[malexanderlim]

@mroy-seedbox happy to share that a basic integration is in place! Do you have any triggers or actions that you'd like to see for Talend? Given the breadth of their APIs, some input for developing components would be helpful to ensure that we are solving the right use cases for you.

[mroy-seedbox]

Trying it now!

FYI: There's a typo in the app setup/credentials:

And the typo also affects the code:

[malexanderlim]

Thanks, nice catch! I've updated it to personal_access_token as it should be.

[mroy-seedbox]

Another FYI: Talend is one of those API (along with Tableau) which increments their API versions often (currently v2.6).

Idk what would be the best way to manage that in Pipedream... I'm thinking that setting the API version along with the app would make sense? Otherwise, it would have to be a prop configured for every single action.

[mroy-seedbox]

For the actions, we currently just use two of them (and no triggers for now):

Execute Plan:

    const response = await axios({
      method: "POST",
      url: `https://api.us.cloud.talend.com/tmc/v2.6/executions/plans`,
      headers: {
        "Authorization": `Bearer ${this.talend.$auth.personal_access_token}`,
        "Content-Type": "application/json",
      },
      data: {
        "executable": this.planId
      },
    });

Get Plan Execution Status:

    const response = await axios({
      method: "GET",
      url: `https://api.us.cloud.talend.com/tmc/v2.6/executions/plans/${this.execution_id}`,
      headers: {
        Authorization: `Bearer ${this.talend.$auth.personal_access_token}`,
      }
    });

[malexanderlim]

Thanks for the detail @mroy-seedbox , I've created https://github.com/PipedreamHQ/pipedream/issues/7674 for tracking development of these components.

In addition, instead of the endpoints that you shared (which appear to now be legacy), I've included documentation for the latest version for the actions shared - which include version headers in the YYYY-MM format. I will close this ticket for now, so please follow along at the component ticket to watch the progress!