This topic was automatically generated from Slack. You can find the original thread here.
If I create a custom domain will it create email triggers on that domain?
Creating a custom domain in Pipedream allows you to configure HTTP endpoints to be accessible via a domain you own, rather than the default [pipedream.net](http://pipedream.net) domain. This is particularly useful for HTTP triggers in workflows, where you might want to use a more branded or recognizable domain for your HTTP requests. However, creating a custom domain for HTTP endpoints does not directly create or affect email triggers. Email triggers in Pipedream are based on a specific email address generated for your workflow, not a domain. When you use the Email trigger, Pipedream generates a unique email address for your workflow. Any email sent to this address triggers your workflow, and Pipedream parses its body, headers, and attachments into a JavaScript object. This process is separate from the configuration of custom domains for HTTP endpoints. If your goal is to trigger workflows based on receiving an email to a specific address under your custom domain (e.g., [info@yourcustomdomain.com](mailto:info@yourcustomdomain.com)), you would need to set up email forwarding from your email provider to the unique Pipedream email address generated for your workflow. This way, emails sent to your custom domain’s email address can trigger the Pipedream workflow. For more information on setting up custom domains for HTTP endpoints, please visit Pipedream’s documentation on custom domains. For details on using the Email trigger, you can refer to the Email trigger documentation.
this is something we’ve discussed internally - do you need this for a specific workflow?
I do need this. I’ve been using ForwardEmail as an outside application for this purpose, but I need to be able to do more with the emails than just forward them. If you guys added this feature, you could effective replace a whole category of production tools. I think it would be a win for a lot of folks!
nice! Will share with the team
I’m trying to use email as a trigger, but I need to maintain my app branding. Thus the significance.
Can I duplicate a folder of workflows?
Based on the provided documentation, there isn’t a direct mention of duplicating a folder of workflows in its entirety. The documentation covers moving workflows into folders and syncing multiple workflows to a single GitHub repository for organization and management, but it doesn’t specify the ability to duplicate a folder with all its workflows at once. To manage your workflows more efficiently or to create backups, you might consider the following approaches: 1. Copying Individual Workflows: You can copy individual workflows into your account. This is useful for public workflows or any workflow you wish to duplicate. Navigate to the workflow you’d like to copy and click the big green Copy button near the top-right corner. This process would need to be repeated for each workflow in the folder you wish to duplicate. Copying Workflows 2. Using Projects for GitHub Sync: If your goal is to have a backup or version-controlled collection of workflows, consider using projects. Projects allow you to sync multiple workflows to a single GitHub repository. This way, you can manage multiple workflows under a single repository for easier organization. Projects and GitHub Sync 3. Moving Workflows into Folders: While this doesn’t duplicate a folder, organizing workflows into folders can help manage them more effectively. You can drag and drop workflows into the desired folder. Moving Workflows into Folders If duplicating a folder of workflows is a critical feature for your workflow management, I recommend reaching out for more personalized support or to suggest this feature. Visit Pipedream Support for further assistance.
We don’t have a method in the UI, but we expose an API for workflows that lets you create a workflow from a template, if that helps