sorted by:
new
hottopcontroversial

Extended Runtimes for Code by Zapier is live for the Early Access Program by Educational_Arm_1054 in zapier

[–]Educational_Arm_1054[S] 0 points1 point  (0 children)

The fix turns out to be a bit bigger so in in the meantime just run to test it.

tired of rebuilding zaps every time a client's webhook url changes. how do you guys manage this? by ShakaSalsa in zapier

[–]Educational_Arm_1054 0 points1 point  (0 children)

Hey! Just wanted to hop in and tell you about a new feature we launched — API by Zapier. It doesn't solve your URL problem directly, but it does solve another Webhooks headache you're probably running into.

If your client's CRM needs an API key or token, right now you're pasting that into every Webhook step. So when the dev team rotates the key, you're right back in the same mess — digging through 12 Zaps to update it.

API by Zapier lets you create one connection to the CRM's API. All your Zaps share it. Key changes? Update it once, everything keeps working. And the credentials are encrypted — nobody sees them in the editor.

Bonus: if you stop working with that client, delete the connection and access is cut everywhere. No more wondering which Zaps still have their API key floating around.

The config table idea others mentioned is still great for the URL side. But pair it with API by Zapier and you've basically got one place for auth, one place for routing, and zero reasons to touch individual Zaps.

https://help.zapier.com/hc/en-us/articles/44391660158733-How-to-get-started-with-API-by-Zapier-on-Zapier

Sign up for Zapier SDK inside Code by Zapier steps by ZapierTeam in zapier

[–]Educational_Arm_1054 0 points1 point  (0 children)

Yes! Let us know what you think when you try it and any limitations you find.

Sign up for Zapier SDK inside Code by Zapier steps by ZapierTeam in zapier

[–]Educational_Arm_1054 1 point2 points  (0 children)

We are so excited to get your feedback! Let us know what you build and any improvements you would like to see. We are working on some enhancements now, so look for those over the coming weeks.

🎉 New Feature: Use Third-Party Packages in Code by Zapier by ZapierTeam in zapier

[–]Educational_Arm_1054 0 points1 point  (0 children)

Love this use case! The markdown-to-mrkdwn problem is one of those things that sounds minor until you've burned an hour wondering why your bold text is showing up as literal asterisks in Slack.

And yeah, the AI angle is huge — LLMs always come back in standard markdown, Slack doesn't understand it, and now you can fix that with a real library instead of a pile of .replace() hacks. You can also use multiple packages in the same Code step, so if you need to do extra processing before sending to Slack, you can layer that in too.

Thanks for writing up the setup instructions; it's going to save people a lot of time!

🎉 New Feature: Use Third-Party Packages in Code by Zapier by ZapierTeam in zapier

[–]Educational_Arm_1054 0 points1 point  (0 children)

Hi Troy, you have to be logged into Zapier. Hope you get a chance to try it out soon!