Create Automations via API
under review
Log In
Mickey Preisach
Zach - thanks for this, however, what about fixing the API first by allowing us to add files to custom fields (that are of a type of an attachment)?
Zach
under review
Hey everyone!
We're trying to better understand the needs here and have come up with a list of potential API requests that you may have. Could you please help me better understand
- Which one(s) are most important to you
- Why? (How would you use this in your workflows)
Thank you!
John
We have several use-cases that require similar but not identical automations. Currently, we have the core of the automation in the template, but whenever we apply the template, we need to go in and modify the integrations for that particular location.
For example, we have different Spaces for each customer. Each Folder in the customer Spaces represents a project, and we have automations that assign various people based on the type of task. Each customer has a unique account team though, so each of these automations assigns a different person in each Space. Currently, when a new customer Space is created, we need to manually modify all of those automations even though the logic is templatized. If each Folder/List has different requirements than the Space as a whole, it magnifies this issue because it would need to be modified each time we create a new project.
So I would think we would need full CRUD access so we can manage these customer Spaces in bulk.
Zach
John It sounds like if we had better remapping, that would solve your issue vs adding API improvements for automations. Is that accurate?
Pete Jackson
another essential missing core feature
Ravi Tharuma
I found a temporary solution for that:
I do it via Make
Mike Wendt
Creating automations automatically for the numerous GitHub repos we maintain as a DevOps team would be very helpful. Otherwise, I have to manually create several of these automations for each new repo we oversee and that does not scale.