TrigCode AI
    TemplatesShowcasePricing
    Help center

    Getting started

    Welcome to TrigCodeBuild your first appChoose an app typeWrite effective promptsNavigate the TrigCode workspace

    Building and editing

    Understand the build lifecycleEdit an app with conversationPreview and test your appWork with code and filesUse checkpoints and rollbackOrganize work with projects and templatesUse reference images and app secrets

    Export and deploy

    Export source codeConnect GitHub, GitLab, or BitbucketDeploy on TrigCodeDeploy to external providersPreview mobile apps and build an APKConnect a custom domain

    Plans, credits, and account

    Plans and feature accessCredits and action costsBilling, renewals, and plan changesAccount and security settings

    Teams and enterprise

    Teams workspacesRoles, budgets, and governanceConfigure SSO and SCIMShared prompts, usage, and audit history

    API and automation

    API authentication and scopesAPI task referenceAPI organization resource referenceReceive signed webhooks

    Troubleshooting

    Troubleshoot builds and editsTroubleshoot previewsTroubleshoot deployments and domainsTroubleshoot billing and creditsGet support
    Help/Troubleshooting/Get support

    Troubleshooting

    Get support

    4 min readReviewed 9 September 2026

    Choose the right support path and include useful, secret-free evidence.

    On this pageSupport pathsInclude enough contextNever send secrets

    Support paths

    PathBest for
    Workspace SupportSigned-in product, build, account, or billing tickets with ongoing replies.
    Contact pagePublic product questions, sales, or access enquiries.
    support@trigcode.comA direct support email when you cannot reach the workspace.
    Trust & SecurityCurrent platform security and compliance scope before a technical review.

    Include enough context

    • A concise subject and the affected workspace or task short ID.
    • Expected versus observed behavior.
    • Exact error text and approximate time with timezone.
    • Steps to reproduce once.
    • Browser/device details for interface issues.
    • Payment reference for billing issues.

    Never send secrets

    • Passwords, passkey material, TOTP setup secrets, backup codes, or OTPs.
    • Full API keys, webhook signing secrets, provider tokens, or cloud credentials.
    • Complete card or bank details.
    • Private customer data or source files unrelated to the issue.
    Support will not need your password

    If a fix requires an account action, perform the authentication step yourself in the product or provider interface.

    Still need help?Open a support ticket from your workspace or contact the TrigCode team.
    Contact support

    Related guides

    Troubleshoot builds and editsRespond safely to stalled progress, failed validation, model errors, and incorrect output.Troubleshoot deployments and domainsSeparate preview success from packaging, provider, DNS, and production failures.Account and security settingsManage profile, password, passkeys, phone, two-factor authentication, and sessions.
    PreviousTroubleshoot billing and credits

    On this page

    Support pathsInclude enough contextNever send secrets
    TrigCode AI

    Bring your ideas to life with AI.
    Build, refine, and make them yours.

    Start building

    Product

    • AI app builder
    • Templates
    • Showcase
    • Pricing
    • Teams & enterprise

    Build

    • Websites
    • Web apps
    • Mobile apps
    • Games
    • Dashboards
    • CRM
    • SaaS
    • Scheduling
    • AI assistants

    Resources

    • Help center
    • Building guides
    • Compare builders
    • Vibe coding explained
    • What you can build

    Company

    • About TrigCode
    • Contact us
    • Trust & security
    • Get support

    © 2026 THS CyberSecure Private Limited.All rights reserved.

    Privacy policyTerms of service