Import a Google Form as a native form and database
Copies a Google Form into a new native Snoze form plus a purpose-built backing database for its responses, and reports the questions that had no native equivalent. This is a one-time structural copy with no ongoing link to the provider. Requires the provider read permissions the underlying resource read enforces, plus permission to create the form and database. A resource that is not a Google Form, or a form with no importable questions, is rejected. Send an `Idempotency-Key` header to make retries safe; a replay within the window returns the original response.
Authorization
apiKey Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.
In: header
Path Parameters
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
curl -X POST "https://example.com/v1/workspaces/string/integrations/resources/import-form" \ -H "Content-Type: application/json" \ -d '{ "connectionId": "string", "resource": { "externalType": "string", "externalId": "string", "name": "string", "surfaceKind": "generic", "capabilities": [ "browse" ] } }'{ "data": { "surfaceId": "string", "itemId": "string", "databaseId": "string", "title": "string", "fieldCount": 0, "skipped": [ "string" ] }}{ "_tag": "ApiNotFound", "error": "not_found", "message": "That item does not exist, or this key cannot see it.", "status": 404}{ "_tag": "ApiNotFound", "error": "not_found", "message": "That item does not exist, or this key cannot see it.", "status": 404}Mount a provider resource into the workspace
Creates a mount for a browsed provider resource so its content is mirrored into the workspace rather than merely linked, optionally recursively and under `parentItemId`, and returns the resource with its placement and mount. Requires both the `resources:write` and `integrations:write` workspace permissions. Send an `Idempotency-Key` header to make retries safe; a replay within the window returns the original response.
Import a provider resource as a native database or page
Copies one browsed provider item into native Snoze content — a Notion database becomes a database with its records, a Notion page or a ClickUp list or a Jira project becomes the matching native surface — and reports the structures that had no native equivalent. The result is fully editable and not live-linked; re-importing the same resource refreshes it in place because records key on the provider's external id. Requires the provider read permissions the underlying resource read enforces, plus permission to create the resulting content; other resource types are rejected as unsupported. Send an `Idempotency-Key` header to make retries safe; a replay within the window returns the original response.