I heard you guys are working on a make.com integration, woohoo! This will solve a ton of complex make scenarios we’re building right now that are so fragile if anything on the pickaxe API side changes.
Any word on timeline on pushing it live so we can plan? 
Wanted to start a community discussion around TRIGGERS that be awesome to have (like a Make Wish List)
#1 top wish list item for me would be having a new user created (instant) trigger
• right now the workaround @ab2308 showed me is so complex it has to pull a list of a bunch of users every 15min, split the array into bundles, compare the date to the most recent date in a spreadsheet, and then from there it can determine which users are “new” vs ones we already have in system. It’s super complex and also very costly. I’ve used 2000 operations on Make in less than 24hrs just setting it up and testing.
With most SaaS being sold in a “product first” way this would be a crucial step to helping PickAxe go mainstream - I want to drive traffic right to my pickaxes directly and have them create leads for the business, build my list, and eventually sell the subscription. But for that to happen (and it to be done well), I’d love this one ASAP 
**#2 would be triggers on purchases or plan changes
**
Right now there’s no great way to send this data externally outside of the above method and a bunch of filtering and rulesets. Having an instant purchase or plan change trigger would be incredible. When people buy I want to send them near instant emails within minutes (sticking the sale and this will allow us to do that.) If this is just a trigger on a plan change that might be more versitile as you could use it for downgrades, as well.
**#3 Memory Updates
**
This would be so epic. Right now you can get a list but it’s hard to get updates with specific users in real time without complex api calls. Having it as a simple instant trigger in Make would make it a lot more versitile. The memory feature is one of those stand out crazy awesome features that will be so valuable - imagine having a make.com automation that pulled updated user memories into a knowledge doc that your marketing team could use to know exactly what your user’s pain points, language patterns and needs are. Or being able to update a CRM with user memory so on a sales call or client success call the rep/coach could hyper personalize the experience.
4. Anything else that’s in the current API but with all the fields in the API accessible
For example CREATE USER (in current API) has the upside of being easy for the client, but you can’t set their NAME
And INVITE USER (in current API) has the upside of having the name field, and the convenience of landing in their inbox (hopefully! it’s been hit or miss for me) but the inconvenience of the user having to reset their password, and as a studio you have to find a way to communicate it to them through another email through a separate service.
To truly scale it’d be awesome to have both of these in Make with all the options in the current api (name, createdat, products, etc)
On the Make topic:
Thinking ahead for external connections, on the sign up form to be able to split first name and last name as seperate fields - they can be seperated on Make later but a lot of CRMs have them as separate fields so when you send emails you can say “hey John” not “hey John Smith”
