feat(integration): add timezest support #5045
Open
+79
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
hassan254-prog
left a comment
hassan254-prog
left a comment
There was a problem hiding this comment.
This looks good, same comments from the other pr 5044 also apply here.
Contributor
There was a problem hiding this comment.
Consider placing this logo within a 64×64 px square constraining the logo’s max width or height to 44 px.
Comment on lines
+56
to
+60
| ### Additional Notes | ||
|
|
||
| - TimeZest recommends generating a separate API key for each integration to limit exposure if credentials are compromised | ||
| - API keys can be revoked immediately by deleting them from the API Keys settings page | ||
| - Authentication is done using Bearer token format: `Authorization: Bearer <API Key>` |
Contributor
There was a problem hiding this comment.
safe to omit these here as its not required.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds support for timezest scheduling platform
Add native TimeZest integration provider and accompanying docs
This PR introduces first-class support for the TimeZest scheduling platform. A new provider entry allows users to authorise TimeZest via OAuth and consume its actions/triggers through the UI and SDK. Comprehensive documentation, code snippets and brand assets were added so the integration is discoverable and easy to adopt. The change set is purely additive and does not modify core runtime logic or existing providers.
Key Changes
• Added
timezestentry to packages/providers/providers.yaml• Created docs/integrations/all/timezest/connect.mdx with setup instructions and scopes
• Regenerated auto-generated snippet files so TimeZest appears in integration lists
• Added TimeZest PNG logo asset referenced by docs
Affected Areas
• Provider registry (providers.yaml)
• Developer & end-user documentation
• Static assets pipeline (logo inclusion)
This summary was automatically generated by @propel-code-bot