> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/thermal-imagery-ai/admin/core-functions/didge-set-up/operation-set-up.md).
# Operation Set Up
Setting Up an Operation in the Didge Platform with Google Drive Integration
Applies To: Didge Platform – Admin Console
Purpose: To configure an operation using a custom form and link it to a Google Drive folder for automated image ingestion
***
### 1. Purpose
To establish an operation within the Didge Platform that links a preconfigured AI-ready form to a Google Drive folder. This setup enables the Didge system to automatically listen for and process new images added to the specified Google Drive folder.
***
### 2. Prerequisites
* Admin-level access to the Didge Platform
* A completed form created for AI data extraction
* A shared Google Drive folder (for incoming images)
* A shared link from that Google Drive folder
* Reliable internet access
***
### 3. Step-by-Step Setup Procedure
#### Step 1: Access the Admin Panel
* Log into the Didge Platform.
* Navigate to the Admin section in the dashboard
#### Step 2: Create or Add Operation
* Select “Add Operation”.
* Enter a name for your operation (e.g., “Thermal Image Intake”).
* Optionally, you can also create this as a Resource depending on workflow requirements.
#### Step 3: Link Your Custom Form
* In the Form Selection area, choose the AI-enabled form you previously created.
* This form should include:
* A file upload field for the image
* Text/number fields with ChatGPT prompts in their descriptions
#### Step 4: Configure Google Drive Listening
* Scroll down to Advanced Settings.
* Locate the setting labeled “Drive to Listen”.
* You will see two fields:
1. Didge-generated share link – copy this link
2. Field for Google Drive link – paste your shared Google Drive folder link here
#### Step 5: Link Google Drive to Didge
* Open your Google Drive and locate the folder where images will be saved (e.g., via IFTTT or manual upload).
* Right-click the folder and select “Share”.
* Set sharing permissions to “Anyone with the link can view”.
* Remove the query string from the share link
* Copy the share link and paste it into the “Drive to Listen” field in Didge.
#### Step 6: Link Didge Back to Google Drive (Optional)
* To complete the handshake, paste the Didge-generated link into the Google Drive folder description or reference location if tracking bi-directional access.
***
### 4. How It Works
Once this setup is complete:
* The Didge system will check the linked Google Drive folder every 10 minutes.
* Any new image file placed in that folder will be automatically imported.
* The image will be processed using the associated form and AI extraction rules (based on field descriptions).
* Extracted data is then populated into the form fields and saved as a completed entry in Didge.
***
### 5. Notes & Best Practices
* Ensure Google Drive sharing is maintained — restricted permissions will break the sync.
* Use clear naming conventions for folders and operations (e.g., “Inspection\_Uploads\_Apr2025”).
* Didge processes images asynchronously — allow up to 10 minutes for ingestion.
* The image source folder can be fed by IFTTT, mobile camera apps, or manual uploads.
***
### 6. Maintenance & Troubleshooting
| Issue | Solution |
| ------------------------------ | ------------------------------------------------------------------------------------------------- |
| Images not appearing in Didge | Check if Google Drive link has expired or permissions were changed |
| Wrong form linked to operation | Edit the operation settings and update the form |
| Multiple files not syncing | Confirm that the folder is still publicly accessible and file types are supported (JPG, PNG, PDF) |
| Drive-to-Didge delay | Wait for 10–15 minutes; check if Didge is still actively polling the folder |
***
### 7. Confirmation & Testing
* Upload a test image into the shared Google Drive folder.
* After 10 minutes, confirm:
* Image appears in Didge under the linked operation
* AI extraction fields have been auto-populated correctly
* Data is stored and viewable in the Didge form submission list
***
Would you like a downloadable PDF version of this SOP or a one-page visual workflow summary to accompany it?
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.didge.io/home/thermal-imagery-ai/admin/core-functions/didge-set-up/operation-set-up.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
