> ## Documentation Index
> Fetch the complete documentation index at: https://atmet.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Atmet FAQ: Common Questions About the Platform Answered

> Answers to the most common questions about getting started, connecting apps, billing, security, and how Atmet works under the hood.

Find answers to the most common questions about Atmet below. If your question isn't covered here, reach out to the team through the in-app chat or visit [atmetai.com](https://www.atmetai.com).

<Accordion title="How do I get access to Atmet?">
  Atmet is currently in early access. To request an account, join the waitlist at [atmetai.com/waitlist](https://www.atmetai.com/waitlist).

  Once the team approves your application, you will receive an email with a one-time password (OTP). Use that OTP — along with your email address — to sign in for the first time. After your first sign-in, you can set a password for future logins.

  <Note>
    Check your spam or promotions folder if you don't see the OTP email within a few minutes of being approved. OTPs are time-limited, so use it promptly.
  </Note>
</Accordion>

<Accordion title="What apps can I connect to Atmet?">
  Atmet supports 20+ integrations out of the box, covering communication, productivity, project management, CRM, and developer tools. Current integrations include:

  * **Communication:** Gmail, Slack, Telegram, Discord, X (Twitter), Instagram
  * **Productivity:** Google Drive, Google Sheets, Notion
  * **Developer tools:** GitHub
  * **Project management:** Jira, Asana
  * **CRM & sales:** HubSpot, Salesforce

  New integrations are added regularly. Check **Settings → Integrations** inside your workspace for the full up-to-date list and connection instructions.
</Accordion>

<Accordion title="Do I need to write code to use Atmet?">
  No — Atmet is designed to be used without writing a single line of code. Describe what you want your automation to do in plain language inside the agent chat, and Atmet figures out the steps, tools, and integrations needed to get it done.

  For developers who want deeper control, Atmet also exposes a REST API and supports custom scripting within workflows. But coding is entirely optional — most users build powerful automations through natural language alone.
</Accordion>

<Accordion title="Can I use my own OpenAI or ChatGPT API key?">
  Yes. Atmet supports **Bring Your Own Key (BYOK)** for OpenAI. Connecting your own key lets you use your existing OpenAI quota and billing instead of consuming Atmet's shared capacity.

  To connect your OpenAI key:

  1. Go to **Settings → Integrations**.
  2. Find **ChatGPT / OpenAI** and click **Connect**.
  3. Paste your OpenAI API key and save.

  Once connected, Atmet routes applicable model calls through your key.
</Accordion>

<Accordion title="What AI models does Atmet support?">
  Atmet supports multiple AI models, including models from the OpenAI family (such as GPT-4o and GPT-4 Turbo). You can choose which model powers each workflow or agent conversation, allowing you to balance capability, speed, and cost based on your use case.

  Model availability may vary by workspace plan. Check the model selector in the agent chat or workflow builder to see which models are available on your current plan.
</Accordion>

<Accordion title="How does billing and pricing work?">
  Atmet is currently in early access, and pricing is not yet publicly listed. To discuss pricing for your team or organization, contact the Atmet team directly through the in-app chat or by visiting [atmetai.com](https://www.atmetai.com).

  Each workspace has usage limits based on its plan — you can review your current consumption under **Settings → Workspace → Usage**.
</Accordion>

<Accordion title="Is my data secure?">
  Yes. Atmet is built with security as a core requirement, not an afterthought:

  * **Credentials are encrypted at rest.** All OAuth tokens, API secrets, and other credentials are stored encrypted and are never logged or exposed in plaintext.
  * **API keys are never recoverable after creation.** When you create an API key, it is displayed once and never stored in a recoverable form. If you lose a key, you must revoke it and generate a new one.
  * **Webhook endpoints verify signatures.** Incoming webhooks are validated against a cryptographic signature before being processed, preventing spoofed requests.

  If you have specific security or compliance questions, contact the Atmet team.
</Accordion>

<Accordion title="What is workspace memory?">
  Workspace memory is a persistent knowledge store that lets your AI agents remember information across all workflows and conversations. You can use it to store:

  * Your team's preferences and working style
  * Rules and constraints agents should always follow
  * Background context about your business, products, or customers

  Instead of re-explaining your context every time you start a workflow, agents automatically draw on workspace memory to act consistently and intelligently from the start.

  Manage your workspace memory from **Settings → Memory** inside your workspace.
</Accordion>

<Accordion title="Can my whole team use the same workspace?">
  Yes — workspaces are designed for team collaboration. Invite as many teammates as your plan supports, assign each person a role (`owner`, `admin`, or `member`), and everyone can build and run automations together in the same shared environment.

  Shared workspaces mean your team's integrations, agents, and workflows are all visible and accessible in one place, without duplicating setup across individual accounts.

  See [Manage Workspace Members](/workspace/members) for step-by-step instructions on inviting teammates and managing roles.
</Accordion>

<Accordion title="What happens when a workflow fails?">
  Every workflow run — whether successful or not — is fully logged. When a run fails:

  1. Atmet records the exact step that failed and the error details.
  2. A failure indicator appears on the workflow in your dashboard.
  3. Open the workflow and navigate to **Runs** to review the log for that execution.
  4. After fixing the underlying issue (for example, reconnecting an integration or correcting input data), you can re-run the workflow from the management panel.

  <Tip>
    Check the run log first before making changes — most failures are caused by expired integration tokens or changed data formats that are easy to resolve once identified.
  </Tip>
</Accordion>