![]() ![]() ![]() The Google Apps Script bridges the SendSafely Dropzone and the Zendesk platform. Step 3 - Configure and Deploy the Connector in Apps Script If you have not already done so, follow the instructions outlined here to turn on your SendSafely Dropzone. On conversion, we require the customer to generate a new API token upon transitioning to a self-hosted connector. Note that SendSafely will, under certain circumstances, host a prospective customer’s connector for them during a pilot period. Under "Token Access" press the "+" button to obtain a new token.įor security purposes, SendSafely recommends regularly rotating API tokens. In Zendesk, go to Admin > Channels > API > Settings. For this step, you'll need to be logged into Zendesk with the identity you want the connector to use for updating tickets. Obtain a Zendesk API Token for the connector script to use. You should host the Google Apps Connector in your Google Workspace environment.įor additional help or questions, contact Step 1 - Obtain a Zendesk API Token Below are the steps for creating and configuring a Dropzone connector for Zendesk using Google Apps Script. The Dropzone connector can be facilitated using Google Apps Script, AWS Lambda or our Zapier App. This value can either be entered by the customer at the time of Dropzone file submission, or, more commonly, embedded in the Dropzone URL provided to the customer by the agent. The connector uses the Dropzone lookup field (TicketID) to associate inbound files with the appropriate ticket in Zendesk. Once configured, the connector updates existing Zendesk tickets with SendSafely secure links for file downloads. The Connector is available on the SendSafely Business and Enterprise plans. Ok ok, let's add the JavaScript to make it actually work.Our Dropzone Connector for Zendesk allows you to integrate your SendSafely Hosted Dropzone with Zendesk. Dropzone block is just a DIV with ID and some classes, how will it actually work?.Full form is gonna be submitted to projects.store route - we will get to that later. ![]() There are multiple ways to do it, depending how you structure your whole Blade architecture, but here's my version of resources/views/admin/projects/: Name/Description fields, irrelevant for this article -}} In our Blade file, with the form, we need to add JavaScript code for Dropzone. This table uses Polymorphic Relations, so in our case will store records with model_type field equals app/Models/Project, which means that media file will be assigned to a project (not to a user, or anything else). Next, we publish their migration files, and run migrations: php artisan vendor:publish -provider="Spatie\MediaLibrary\MediaLibraryServiceProvider" -tag="migrations"īy this time, we should have media table in our database. We install the package like this: composer require spatie/laravel-medialibrary:^10.0.0 Let's prepare the back-end, where we will actually store the files. A simple for to add Projects, where you can also upload multiple files for every project.Īs you can see, file upload has a big block instead of just an input file field. Let's take two of my favorites - Dropzone on the front-end, and Spatie MediaLibrary on the back-end, and build a great uploading experience, in this tutorial.įirst, what we're building here. And we have quite a few libraries that can help us to build upload form. File upload is one of the most popular features in modern web.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |