Paragon Q3 2024 Product Update Webinar
Watch Ethan (Director of Product) and Nick (Product Manager - Integrations) walk through some of the major updates we've made to the product this quarter.
Summary
Our product team walks through some of the latest updates to the platform in this webinar, including - below is a high level overview of each feature, as well as a summary of the Q&A.
Custom Webhooks
Allows creation of webhook listeners for any HTTP webhook API
Triggers Paragon workflows from custom events in integrated applications
Implemented through a wizard in the workflow editor
Extends trigger capabilities beyond native Paragon events
Get early access here
Resources
Enables defining and reusing API configurations across workflows
Supports various authentication methods (OAuth, API keys, custom)
Allows creation of custom triggers and workflow actions
Currently in private beta (join beta here)
Paragraph CLI Updates
New interactive push command for deploying code-based representations
Displays a changelog of effects before pushing
Warns about potential deployment issues (e.g., missing environment secrets)
Smart Rate Limits
Automatically manages rate limits for third-party API requests
Tracks requests and backs off when approaching limits
Handles 429 status codes (rate limit exceeded) appropriately
Currently supported for Salesforce, NetSuite, and Gmail, with more integrations planned
No opt-in required; applied automatically to supported integrations
Q&A
Is custom webhook supported in custom integrations as well?
Yes, custom webhooks are supported for both native and custom integrations.
Do triggers for resources replace app events?
Resource triggers do not replace app events - resource triggers offer an easier implementation for customers with existing webhook systems.
App events are still useful for triggering workflows across multiple integrations.
Just to confirm, we can use both the visual editor and the code framework, or do we have to pick one?
Yes, users can use both the visual editor and the code framework (Paragraph). Our two-way sync allows for bidirectional updates between code and visual representations via Git. Teams can choose to primarily use one or the other based on preference, but again both can be used interchangeably.
With the interactive push commands, would we still promote projects to staging via the dashboard?
The new push command is for deploying code changes to the Paragon platform, whereas Releases are still used for promoting projects from development to staging/production. Releases provide additional staging/production considerations and maintain historical artifacts, but the team is considering ways to bring more dashboard workflow features into the Paragraph CLI.
