We never keep your screenshots as the primary source of truth. Cloud storage integrations let you send every capture directly into your own Google Drive, Dropbox, or S3 buckets.

Cloud Storage Profiles

Cloud Storage profiles represent connection settings for a specific provider. Each profile has:

• An Cloud Storage Profile Name.
• A Provider (e.g. Google Drive, Dropbox, AWS S3).
• An IsActive flag.
• Optional defaults (First/Second/Third) to mark which profile is preferred for particular slots in Web Profiles.

Supported providers

Depending on your plan and configuration, you can connect:

• Google Drive – ideal for teams and clients.
• Dropbox – great for clean folder-based archives.
• AWS S3 – built for large volumes and pipelines.

Health & status

Each Cloud storage profile can expose a health flag, indicating if the connection is working (e.g. token still valid, bucket reachable):

• IsHealthy = true: integration is ready to receive files.
• IsHealthy = false: something needs attention (permissions, expired keys, etc.).

Linking to Web Profiles & schedules

Web Profiles reference cloud storage and one or more Cloud Storage Profiles. When a schedule uses that Web Profile:

• Captures are delivered to the configured integration (e.g. a specific Drive folder or S3 bucket).
• If a default profile is marked (FirstDefault/SecondDefault/ThirdDefault), the system knows which integration to prefer.

Best practices

• Create one Cloud Storage Profile per destination (e.g. “Legal S3 Bucket”, “Marketing Drive Folder”).
• Use Web Profiles to decide which destinations match which page types.
• Periodically review health flags and permissions, especially after rotating keys or credentials.