1
Request access
Atmet is currently in early access. If you don’t have an account yet, visit the waitlist page and submit your request.Once you receive your access confirmation email, you’re ready to sign in.
Join the Atmet Waitlist
Request your early access spot. We’ll email you when your account is ready.
2
Sign in to Atmet
Open the Atmet app and sign in with your email address.
Sign In to Atmet
Access the Atmet app at app.atmetai.com.
- First-time sign-in
- Returning user
Enter your email address and click Continue. Atmet sends a one-time passcode (OTP) to your inbox. Enter the code to complete sign-in.
3
Create your workspace
After signing in for the first time, Atmet prompts you to create a workspace. Your workspace is the shared environment where all your integrations, workflows, skills, and team members live.
- Enter a workspace name, this is typically your company or team name.
- Optionally select your country to help with locale-aware automations.
- Optionally upload a workspace avatar to make it easy to identify at a glance.
- Click Create Workspace to continue.
You can update your workspace name, avatar, and settings at any time from the Settings panel.
4
Connect your first app
Before the agent can automate anything, it needs access to at least one app. Head to the Integrations panel to connect your tools.Once connected, the app appears as Active in your integrations list, and its triggers and actions become available to your agent.
- Click Integrations in the left sidebar.
- Browse or search the integrations catalog and click the app you want to connect.
- Authenticate using one of the supported methods:
- OAuth (recommended)
- API key
Click Connect and complete the OAuth flow in the pop-up window. Atmet requests only the permissions it needs for the triggers and actions you use. No passwords are stored.
5
Describe your workflow to the agent
With an app connected, open the agent chat and tell it what you want to automate, in plain language, the same way you’d explain it to a colleague.Click New Chat (or the chat icon in the sidebar) to start a conversation with the Atmet agent.Here are a few examples of how to describe a workflow:
6
Answer the agent's questions
After you describe your workflow, the agent analyzes your goal and may ask clarifying questions before it builds the plan. This is normal, it’s gathering the details it needs to make the automation accurate.Common questions the agent might ask:
- Which Gmail account or label should it monitor?
- What should it do if a required field is missing from the trigger data?
- Should it run for all messages, or only ones matching a specific condition?
If the agent needs access to an app you haven’t connected yet, it will prompt you to add the integration before continuing.
7
Review and approve the workflow
Once the agent has enough information, it presents a complete workflow plan for your review. Read through the steps carefully before approving.
- Trigger, The event that starts the workflow (e.g., new Gmail message).
- Steps, Each action the agent will take, in order.
- Conditions, Any filters or branching logic applied.
8
Watch it run
Your workflow is now live. The next time the trigger fires, Atmet executes it automatically, no action required from you.To monitor your automation:
- Click Workflows in the sidebar to see all your active automations.
- Click any workflow to open its detail view.
- Navigate to the Runs tab to see every execution, the steps it took, and its outcome.
What’s next?
Now that your first automation is running, here are a few good next steps:Explore Core Concepts
Understand agents, workflows, triggers, actions, skills, and workspace memory, the building blocks behind every automation.
Browse Integrations
Connect more apps to unlock additional triggers and actions for your automations. 20+ integrations available.
Set Up Workspace Memory
Give the agent persistent context about your preferences, approval rules, and team knowledge so it performs better over time.
Invite Your Team
Add team members to your workspace with owner, admin, or member roles so everyone can collaborate on automations.