@OmarAlmonte Is the current plan to eliminate support for running Actionsets from the API?
Actionsets have the distinct benefit over Campaign sequences in that they run immediately and complete before returning, which is advantageous in many situations.
@David_Bullock Yes — this is legacy functionality, and it was decided not to move forward with it. Refer to: https://learn.thryv.com/hc/en-us/articles/40566846578573-XMLRPC-Endpoints-Not-Being-Converted-to-REST-v2
Can you share the specific scenario where you were using Actionsets?
@OmarAlmonte I suspect you misunderstood the question.
I am looking for: a clear answer as to what the team’s intentions are.
If you’re going to abandon the functionality, that’s up to Keap I’ll let the customers know it’s being dropped, and I’ll rip out all the code, and we’ll find them different solutions.
If you’re going to support Actionsets I need that clarity and information so I can port the code over to the new API.
As I mentioned, there are no plans to port Actionsets to REST v2, as it is legacy functionality.
If you can share your use case, I’d like to understand it so we can see if there’s an alternative approach that would work for you.
My apologies, that was my mistake.
To be frank, I’m so annoyed with Keap at the moment that I I saw the 2nd part of your answer, and didn’t scroll up to see the first part. Stupid mistake, but it was MY stupid mistake.
We’ve been working with Keap / API for 15+ years, we can solve the functionality problems ourselves. We’ll sort it out and find other solutions for our customers.