This topic was automatically generated from Slack. You can find the original thread here.
If someone from Pipedream’s team could take a look at the above-mentioned issue, it would be greatly appreciated. 
Thank you! Addressing this issue would save me from having to create a separate lambda function outside of the workflow.
Hey , Pipedream team is responsible for the native sources/actions such as Slack - New Message, AWS - Download from S3.
From platform perspective, Pipedream team provide environment for user to execute the code, but not responsible for the code by users. So we have limited support for custom code.
As I suggested earlier, you can investigate another way to pass tmp dir to your code.
You can ask our bot @U05A7KLNALC for the coding questions you have (though please note it has the rate limit for usage)
If you found it is a bug on Pipedream platform, kindly compose the minimal reproduce steps then create a ticket here
It seems like you’re looking for clarification on the support provided by Pipedream for native sources/actions and custom code, as well as how to report a bug. Here’s a detailed response based on your query: ### Native Sources/Actions Pipedream provides a variety of pre-built sources and actions, such as: - Slack - New Message - AWS - Download from S3 These components are maintained by the Pipedream team. If you encounter any issues with these native components, you can report them as bugs. ### Custom Code Pipedream provides an environment for users to execute custom code, but the Pipedream team does not offer extensive support for custom code written by users. Users are encouraged to investigate and debug their custom code independently. ### Temporary Directory For operations involving temporary files, you should use the /tmp directory. This is the only writable directory available in Pipedream’s execution environment. ### Reporting Bugs If you believe you have encountered a bug on the Pipedream platform, you can report it by following these steps: 1. Compose minimal reproduction steps. 2. Submit a bug report on GitHub using the following link: Create a ticket here. ### Additional Support For more support options, you can visit Pipedream Support. ### Example Component Code If you need to write a component that interacts with an API, here is an example for Slack: ```
import { axios } from “@pipedream/platform”; export default defineComponent({ props: { slack: { type: “app”, app: “slack”, }, }, async run({ steps, $ }) { return await axios($, { url: https://slack.com/api/users.profile.get, headers: { Authorization: Bearer ${this.slack.$auth.oauth_access_token}, }, }); }, });
thanks for your help. I understand you point, but I am pretty sure there is a little thing blocking the connection ion pipedream’s side. Perhaps someone in the tech team can take a a look. Another option: add MotherDuck as a native integration. Given that the issue has been reported previously, I don’t think I am the only one struggling with MotherDuck connection in Pipedream. But I will continue my investigation and will let you know
You can request a new integration here https://github.com/PipedreamHQ/pipedream/issues/new?assignees=&labels=app%2C+enhancement&projects=&template=app—service-integration.md&title=%5BAPP%5D