Just some suggestions for future consideration - things I would find useful. I realize there’s always more work than time and resources allow!
Re #2 - for example, I’d like an easy way to turn a task into a pipeline. We get phone calls from Jill’s Office, which (via Zapier) get turned into a LACRM task. Sometimes I want to just complete them, but sometimes I want to create a pipeline from the task. Since completing the task and creating a new pipeline are separate actions, if I want the task context to go to the new pipeline, I’m copying details to clipboard before clicking out of the task, completing it, running an automation, editing the pipeline that was created, pasting the details.
Thanks for sharing those suggestions! We do appreciate hearing suggestions for improvement; like you said there’s always more ideas than we can get done, but hearing feedback is really helpful.
For firing a Zapier event from an automation, can you share a bit more detail about what you have in mind? If your automation includes adding to a group, that could be used as a Zapier trigger, but that is a bit limited so I’m curious if you have any other specific examples in mind.
I’m afraid we’re unlikely to add a way to run an automation when a task is completed, sorry about that. Triggering an automation by task completion gets a bit tricky because there would need to be some logic to identify which tasks do trigger an automation, and which don’t. It sounds like you’re already doing this, but the workaround would be to trigger a manual automation to create a pipeline, complete the task, and then copy/paste details as necessary.
We had discussed setting field values as part of automations originally, however, that was cut from the project in the interest of getting automations out more quickly. That is still on our list as a potential improvement for the future, but that isn’t currently prioritized so we don’t have a timeline on when something like that might happen.
I’m sorry I don’t have better news for you here! As always we do appreciate your feedback, and please don’t hesitate to share anything else that comes to mind. 
I also would like to be able to trigger a Zapier via an automation, for example to kick off an email campaign in a marketing application.
I appreciate the complexity of triggers. I have used pipelines as a way to trigger zaps. Could this be used as a work around here somewhere?
I also would like automations to be able to add a note to a pipeline, instead of a note to a contact. For example, an action happens inside a pipeline and I want a note added to that pipeline, not the contact. That way if I transfer the pipeline to another contact the note goes with it.
Basically, I’d just like a Zap event for “automation triggered” passing the details of which automation (by name and ID) and which contact ID.
Now that you mention it, now that I figured out how to remove a contact from a group using the API from Zapier, I could probably have the automation add to a group, have a zap watch “Group Membership Addition”, do whatever, and then remove the contact from the group. I’ll experiment with that.
The technical problem I envision is how LACRM could let you identify a particular pipeline to modify, since you can have multiple active pipelines of the same type. Maybe you could watch for "Pipeline Item Status Update” and create a Zapier table to shadow the open pipelines and then call EditPipelineItem via the API, but it seems fiddly. You’d still have to somehow be able to distinguish between different pipelines of the same type in your table.
Yeah, the tricky part about automations for pipelines is know which pipeline item it should apply to. As @tbridgman mentioned, a contact can have multiple pipelines, and there isn’t really a way to designate which one the automation should be applied to. Due to the complexity of that, we don’t have plans to add more automations to the pipeline, sorry about that.
You could potentially work around that using Zapier or the API, like Thomas mentioned, but that would require some programming/setup work. Depending on your pipeline structure/use, you may also need some way to differentiate between different pipeline items if you have multiple on a single contact.
I will bring up the option of adding a note to a pipeline item with the team to see what they say about that!
Hmm yeah, we don’t have any plans to add an option for “automation triggered” generally. The tricky thing about that is the automation is really different actions (adding a task, a note, pipeline, etc). It’s hard to have a Zapier event triggered based on potentially different actions within an automation. That could also potentially end up with an infinite loop of automations; if an automation triggers a zap, that zap could trigger something in LACRM that triggers an automation, which then triggers a zap and so on. I’m sorry I don’t have better news for you on that front!
That could certainly be a workaround, using a group to help trigger a zap. You could have someone added to the group, that group addition trigger Zapier to run an action, and then have them removed from the group.
Sorry about the delay getting back to you here! We did discuss adding the ability to have a note created by an automation added to the pipeline, specifically for automations triggered by a pipeline status. We are hoping to add that feature eventually, but we’re focused on a few other projects now, and I’m afraid I don’t have a timeline on when that might happen. I’m sorry I don’t have better news for you on that!
If you’re curious, Tyler made a video on our 2026 roadmap recently where you can see a sneak peek of our plans for the next year.
fwiw the group add/remove workaround @tbridgman mentioned actually works pretty well. i set up a “zap trigger” group that my automation adds the contact to, zapier watches for group membership changes, runs the zap, then removes them from the group via api. bit hacky but it’s been solid for a few weeks now. biggest gotcha is making sure the zap removes the contact from the group fast enough before you end up with a backlog in there.