Zapier integration

[lepikhinb]

Description

• Manage access tokens (Sanctum)
• Zapier app

Zapier

Install Zapier

npm install -g zapier-platform-cli

Install dependencies

cd `zapier`
npm install

Login to Zapier

zapier login

Register the app

zapier register [TITLE]

Publish the app

zapier push

Set the base URL to receive webhooks from Zapier. The version usually looks like 1.0.0.

zapier env:set [VERSION] BASE_URL=[BASE_URL]

Testing

1. Create an access token: http://localhost:3000/settings/access-tokens
2. Create a Zap
3. Authenticate using your token
4. Submit a form

Summary by CodeRabbit

• New Features

  • Introduced endpoints for managing Zapier integrations, including creating and deleting integrations.
  • Added API token management capabilities, including token creation and deletion functionalities.
  • Introduced a management interface for Access Tokens in the Settings page.
  • Added functionality for listing forms and workspaces through a new API.
  • Introduced a new UI component for managing access tokens.
  • Established a structured approach for Zapier authentication and triggers.

• Bug Fixes

  • Fixed class attributes and event handling in the CopyContent.vue component.

• Improvements

  • Enhanced VCheckbox.vue component to support flexible value types.
  • Improved the integration selection process with clearer user feedback.

• Tests

  • Added test suites for Zapier triggers, including list_forms, list_workspaces, and new_submission.

• Chores

  • Updated dependencies to include laravel/sanctum and pestphp/pest-plugin-laravel.
  • Configured Sanctum for API token management.

[coderabbitai[bot]]

[!CAUTION]

Review failed

The pull request is closed.

Walkthrough

The recent changes enhance the application by introducing new controllers and request classes for managing integrations with Zapier and personal access tokens. New Vue components improve token management, while secure API routes facilitate external interactions. Additionally, the implementation of a database migration for personal access tokens streamlines management. Overall, these updates significantly boost functionality, security, and user experience, making it easier for users to engage with their integrations.

Changes

Files/Paths	Change Summary
app/Http/Controllers/Integrations/Zapier/...	New controllers for managing Zapier integrations, handling creation, deletion, and retrieval of workspaces and forms.
app/Http/Requests/Zapier/...	New request classes for validating operations related to Zapier integrations with specific rules.
client/components/forms/...	Updates to VCheckbox.vue to introduce a new prop for enhanced functionality in forms.
client/components/settings/...	New components for access token management, enhancing the UI with AccessTokenCard.vue and AccessTokenModal.vue.
routes/api-external.php	Established secure API routes for Zapier integrations, including webhook management and data retrieval.
integrations/zapier/...	New modules for Zapier integration, including authentication, triggers for new submissions, and retrieving forms and workspaces.
database/migrations/...	Migration for creating the personal_access_tokens table to structure and manage tokens effectively.
integrations/zapier/package.json	New package.json file, specifying metadata and dependencies for the Zapier integration project.
integrations/zapier/test/...	Introduction of unit tests for various triggers in the Zapier integration to ensure functionality and reliability.

Poem

In lines of code, where dreams take flight,
New features bloom, in day and night.
Tokens, forms, and workspaces align,
Zapier's webhooks, now more divine.
A rabbit's joy, in changes so bright,
Our app evolves, with pure delight. 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.