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.

curl -X POST "https://example.com/v1/workspaces/string/integrations/resources/import" \  -H "Content-Type: application/json" \  -d '{    "connectionId": "string",    "resource": {      "externalType": "string",      "externalId": "string",      "name": "string",      "surfaceKind": "generic",      "capabilities": [        "browse"      ]    }  }'

{  "data": {    "itemId": "string",    "kind": "database",    "databaseId": "string",    "surfaceId": "string",    "title": "string",    "recordCount": 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}