← Automations247

Your team. Your computers.

Automations247 is a testing platform for persistent AI teammates using your own API key or ChatGPT Codex allowance and your own connected Mac or Windows computer.

Use your own API key or ChatGPT subscription

Open Settings and choose your AI connection. For API billing, paste your project key and choose Save API key. For ChatGPT, choose Connect & use ChatGPT, open the OpenAI sign-in link and enter the one-time code. The connection is selected automatically; return to your saved company setup to see its progress. If OpenAI asks, enable device-code login in your ChatGPT security settings. Your plan must allow Codex. Automatic mode chooses from the models OpenAI offers to your connected account; Free plans still have their own usage limits. The connected account and available usage/reset windows appear in Settings.

ChatGPT uses your Codex allowance and its model/usage limits, not API credits. Reaching a limit never silently switches to API billing. Each user supplies their own connection; your key or subscription is never shared with other Automations247 accounts. Disconnect in Settings to remove the connection. ChatGPT chat history and connectors are not imported; connect Gmail and other services in Automations247 separately.

The connection is stored encrypted in your account’s server vault; the isolated runtime uses a private temporary authentication file while running. Prompts, relevant memory, tool results and requested screenshots are sent to OpenAI. Computer work still requires your assigned Mac or Windows worker to be awake and online. Apple users can open web Settings on their phone to connect; new native menu entries require a separate app update. OpenAI authentication details.

Company instructions are saved even before sign-in finishes. Requested team creation continues after your AI connection is ready. First computer assignments show an in-chat setup card for the assigned computer and selected Chrome profile before starting.

Automatic mode tries enabled Qwen Local AI for eligible text work. Simple drafts and text transformations use a tool-free local step with the bot’s standing instructions, company memory and conversation constraints. Research, screenshots, long context and uncertain local results use your selected cloud connection. Each task’s AI usage view records the model used, local-to-cloud handoffs and reasons Local AI was skipped. Local AI requires the optional download on the assigned computer; it is not unlimited free cloud usage.

Optional Local AI

The updated computer worker can offer Qwen3.5 4B through Ollama after pairing and initial setup. Choose Download and enable in the computer’s permission prompt. Allow about 3.4 GB for the model plus the runtime, and at least 10 GB free for setup. Automatic installation currently supports Apple Silicon Macs with macOS 14+ and Windows 10 22H2+ x64 with 16 GB RAM or more. Nothing is downloaded until you agree.

Use Settings → Computer → Local AI for progress, cancel, retry or turning it off. This permission is tied to the paired account on that computer. The model files can be reused across its companies, while each request receives only its own company context; conversation history is not stored as a shared local-model chat. Eligible task instructions and tool results are sent to that assigned computer over the authenticated connection. Downloaded model files remain when you turn it off.

Small automatic text requests can run locally. Larger requests, images, research and fixed model selections use your selected cloud connection. A cloud connection remains required; local AI does not guarantee free automation or fix website interaction failures. Local tokens are listed separately in task usage. Existing installations need a computer-app update once; phones use the assigned computer instead of downloading the model.

Hired does not mean finished

The chat’s Team progress card reads saved employee task states. It distinguishes completed assignments, queued work, working bots and blockers. Open a waiting employee directly from that card. A successful hiring message means the employee was created; it does not prove its assignment or your business operations are complete.

If an employee is waiting because you have manual computer control, opening the screen keeps the bot paused. In the hosted task panel, choose Return control to bots when you have finished. In the native computer screen, choose I’m done. Saved work resumes on the assigned computer. A real sign-in or verification request still requires you to complete the requested action first. Returning control can resume other saved tasks on that same computer.

A computer pause now tells you the saved step waiting to run. You do not need to open an app or do the task yourself for a manual-control pause. For a genuine sign-in request, the bot first opens and inspects the relevant page or app, then explains the human step. If setup or permissions prevent that, it should identify that setup problem instead of claiming a sign-in screen is ready.

Review your team’s work and choose alerts

Open Work log to filter saved assignments by teammate, project, routine, status and updated UTC dates. Open an assignment for original messages, action evidence and manager handoffs. Logging happens automatically. A returning tool result does not prove the business task succeeded. New local attempts record which computer was used; older assignments without this metadata say so. The current workspace label is the current assignment, not historical proof.

Export CSV downloads up to 10,000 filtered assignments with private summaries. Keep the export with people you choose. Raw tool arguments, credentials, screenshots and file contents are excluded. Continuing a conversation can update the same assignment; original messages and receipts remain in its detail view. This log is private to your account, not a new admin view or a shared external board.

In Settings → Alerts from each teammate, choose Results & needs input, Needs input only or Muted. Muting keeps the bot’s work, questions and schedules visible and active. Enable notifications on each receiving computer or installed Home Screen web app. Native Apple management source 0.13.0 (15) adds Work log and Teammate alerts, but requires an updated binary; native TestFlight background push is not available yet.

Teach a repeatable workflow

Choose a teammate in its Computer view and take control. Teach this workflow asks permission to record actions made through that control panel, for up to 10 minutes. Only action types and positions are saved; typed values, addresses, screenshots, clipboard contents and actions on the physical computer are excluded. Stop and review, replace vague positions with meaningful instructions, and add changing names, dates or workspace files. Finish takeover, run an example in Skills and accept its verified result before enabling a linked routine. Changes to the playbook require a new example. Unfinished demonstrations remain private to the selected company and can be discarded in Skills.

Improve a workflow once, reuse it reliably

Tell a teammate what to correct and ask it to remember the improved method. It can update a reusable playbook in chat. In Skills, review its instructions, optional output checks and revision history. Up to 50 revisions are retained privately; restoring an earlier version creates a new revision. Keep passwords and API keys in the existing secure setup areas, never in playbooks.

A routine can link one of its teammate’s assigned playbooks. Each new scheduled, manual or webhook run saves the current revision. Queued runs keep their saved version when the playbook changes. Open a task to see its playbook and checks. Checks tell the AI what to inspect in the actual result; saving them does not prove they passed. Give current corrections in the conversation, and check the reported evidence.

Run now opens an unfinished routine run instead of making a duplicate. If a playbook is missing when a run is queued, cancel that blocked run, restore or choose an assigned playbook and run the routine again. If access was removed after queuing, restore the assignment and explicitly resume to keep the saved version. You can pause the routine while correcting setup. Linking a playbook never grants computer or service access. Apple management source 0.14.0 (16) includes native revision review, restore, routine links and task evidence; a new TestFlight binary is required for those native screens.

Projects, history and usage

Open Projects in the website, or Projects & team conversations from the native app’s Team screen when the updated build is available. Name the project, describe the desired outcome, select up to six existing bots and choose the coordinator. Create & start sends the first assignment immediately. The coordinator can hand work to selected specialists; their actual status, results and blockers appear in the project. Open the exact assignment to answer a question, approve an action or take over its computer. Joining a project does not grant computer or connected-account access.

Projects are private to your account and company. External guest access is not available. Each bot continues using its own assigned computer and signed-in browser profile. Server reasoning, connected APIs and schedules can run while the computer is offline; local app and file work waits for that specific computer. Pause project routines and finish or cancel active tasks before archiving a project.

Use Search work (Command-K or Control-K on a keyboard) to find earlier messages, results, routines, memory and skills in the selected company. Routine run history shows the actual jobs and their outcomes. Settings → Where your API tokens go separates today’s usage from all saved-task usage by bot or routine. OpenAI bills your own API project; token counts are not a price estimate. Chat drafts remain in the website tab through navigation and reload; native drafts last for the signed-in app session. Remote keyboard input and sign-in credentials are never included in chat drafts.

Get started

After signing in, open Settings. The OpenAI API key form is at the top: paste your own project key, choose Save API key, then Test saved key. The Add API key button in chat opens this form. Each account uses its own key; other users never borrow the server owner’s key.

1. Create an account. Use the same account in all your apps. Open your workspace, then Settings for the configuration checklist. New accounts open Settings immediately after signup.
2. In Settings, add your project API key from the OpenAI Platform, save it, and test the connection. API work is billed to your OpenAI account.
3. Install the computer worker on the Mac or Windows PC that should execute tasks. Sign in, pair it and assign it to a workspace.
4. Keep that computer awake. Use Run connection check, then assign a small file-writing task and inspect its real result.
5. Choose your timezone and create a routine. Verify one run before relying on it.

Hire and teach a teammate

You can also tell an existing bot to hire employees, for example: “Hire the catalog, inventory, support, marketing and finance specialists we discussed, and start their assessments.” Each hired employee has its own role, chat, private onboarding memory and first assignment. The manager remembers its team and receives saved results or blockers. Expand Team assignments in the chat to open an employee’s exact work; Details shows the employee roster.

Ask the manager to give an employee a recurring job with a time and timezone. The server saves the routine and the employee compares later runs with earlier successful results. Routine reports also appear in the manager’s Team routine updates conversation. New employees use Results & needs input alerts; change this in Settings. Notification delivery still depends on device support and permission. No native Apple background-push capability is added by this dashboard release.

Employees stay in the selected company and assigned computer. Hiring does not grant terminal, desktop or connected-account access. Review those permissions when needed. Existing employees and their work are reused; a saved assignment is not proof that the job has finished.

Choose Hire a bot and describe what you need. With your saved OpenAI API key, AI fills in the name, role and working instructions using your selected model. This setup call counts toward your daily token limit. Presets and Advanced settings are optional. Without a key, a basic profile keeps your original description.

Open the bot and use Talk to your bot. Ask it to change its responsibilities or remember a preference; changes are saved for future tasks. New desktop, terminal, browser or connected-account access appears in the conversation for approval, even for trusted bots. You can also ask it to remove access. Account sign-in, the global desktop setting and OS permissions still need setup below. Hiring immediately starts a first task from your request. Teammates inspect existing team work, delegate when needed and save requested monitoring as a real server routine. If you ask to keep track without a time, the default is an editable daily 9 AM check in your timezone; the bot reports its saved next run. Reasoning and connected-service tasks can run while your computer is offline. Computer actions wait for the paired worker and required permissions.

Meeting actions and service workflows

In Marketplace, connect ClickUp, Granola, Higgsfield, Firecrawl, Zapier or Blotato for the selected company, then choose the bots and tools that may use each account. Each service uses your own account and plan; service credits are separate from AI usage. OAuth services open sign-in. API-key services show a secure key field and a setup link.

Marketplace → Skills includes Meeting notes to team actions, Team progress tracker, Source to social content, and Website and price watch. Ask your bot to process supplied notes or notes available in Granola. It records agreed actions, assigns specialists, keeps your own decisions separate and reuses those assignments on later scans. Granola must already have the notes; connecting it does not record meetings.

Open All tasks → Action tracker in the web or computer workspace to see owners, deadlines, progress and saved results. You can mark your own action done or open the specialist’s actual task. The panel appears once your bot has recorded actions. Ask for a recurring check with a time and timezone to save a server routine. Desktop and file work still requires the assigned computer to be awake. This hosted panel does not require a worker reinstall; the native Apple app does not yet have a dedicated action-tracker screen.

Use your already signed-in Chrome

In Settings → Computer → Chrome connection, choose your existing Chrome for the workspace. New accounts use this preference. Existing accounts can switch from their separate Bot browser; its saved profile is kept.

1. Update the paired computer worker to 0.15.2.
2. In the Chrome profile where you normally sign in, install Microsoft’s official Playwright Extension. Open the extension and copy its connection token.
3. On that computer, open Automations247 Computer → Settings → Computer → Chrome connection. Paste the token and choose Save on this computer. This token stays encrypted locally and is never uploaded to our server.
4. Choose Check existing Chrome, then select the intended tab for the extension connection. Keep work tabs in that connection’s group. You do not need to sign into websites again just to connect Automations247.

The browser tool reads and acts in connected tabs using their existing profile and cookies. It does not clone your profile, export cookies or fall back to a new browser. OpenAI is used for task reasoning and requested page content; connecting Chrome itself does not make model calls. Requested page text and screenshots can become task history and model input.

Websites can still expire sessions or require human verification. Automations247 pauses and asks you to use Full desktop in the same browser, then continue. It does not solve or bypass CAPTCHA checks. The computer must be awake and online. Phone management works over the server connection; no database or browser token is installed on your phone.

To remove access, choose Disconnect Chrome in the paired computer app or revoke/remove the extension. Computer re-pairing clears Automations247’s local browser token. Signing out of the management app does not stop an already paired worker; disconnect the computer to stop its access.

WhatsApp Web on your computer

Open Connections → WhatsApp Web → Add WhatsApp. Choose your computer workspace, give the account a recognizable name, select its connected Chrome profile or persistent Bot browser, and choose the bots that may use the saved session. Those bots also need browser access in Settings. The website, Android app and Apple app share this setup; in the Apple app open Settings → Connected accounts → Manage.

1. For existing Chrome, add each profile in the computer worker’s Settings → Computer → Chrome connection. Use the profile’s own Playwright extension token. In that Chrome profile, open chrome://version and enter only the last folder name of Profile Path, such as Default or Profile 1. Give the connection a name and check it. Tokens stay in encrypted local storage; only connection names, profile directory names and readiness reach the server.
2. Choose Open / link WhatsApp. Bots pause while you have control. It reopens the WhatsApp tab in the saved browser; it does not switch to another Chrome profile. For a new link, use WhatsApp on your phone → Linked devices → Link a device and scan the QR code displayed on your computer. Check the account and finish takeover. Never put QR secrets or linking codes in chat.
3. Ask: “Using Jodi WhatsApp, summarize today’s unread studio messages and draft replies for review.” Identify the recipient and message when you want a reply sent. For recurring work, ask for an exact time and chat scope. Routines are saved on the server; browser work waits for the assigned computer to be awake and online.

You can save both Chrome and Bot browser entries. Each Chrome profile has its own browser connection. Bot browser entries in the same workspace share one persistent login; use another workspace for another account. Saved sign-in confirmation is your last check, not a live connected guarantee. WhatsApp may expire or revoke a linked session, and the bot asks for linking only after inspecting the page. Pause access or remove a saved entry to stop its use through this feature; removing the entry does not log WhatsApp out. Existing general browser, desktop and terminal grants still access the computer and are not per-chat sandboxes.

This integration operates the visible WhatsApp website. It is not WhatsApp’s Business Platform API, a phone app controller or an always-running cloud inbox listener. Chat content and screenshots requested for tasks are sent to your OpenAI model and retained in task history. We do not export Chrome cookies, copy profiles or implement bulk messaging. Use WhatsApp according to its terms. The browser connection uses Microsoft Playwright’s extension and profile selection.

Type from your phone

Open your computer and choose Take control. Tap the target field on its screen, then use the Keyboard button in the typing bar. The iPhone app includes this bar in normal and enlarged views. Type your text and choose Send to computer; Tab, Enter and Backspace work on the remote field. Hide keyboard returns more space to the computer screen. The website offers the same Keyboard and Send controls.

The phone keyboard can open while the computer is getting ready. Sending still requires a connected, awake computer, a ready preview, active takeover and input permission. Text is masked by default and goes through computer control rather than bot chat. Enable Accessibility on the Mac if sending is disabled because input permission is missing.

Computer permissions

Manual takeover does not need an OpenAI API key. Install and pair your worker, assign it to a workspace, then open Settings → Native desktop control & permissions. Enable the desktop switch and save, select the workspace, and check its computer. Screen capture and input permissions are reported separately. Requests go to that computer, even when you use Settings from your phone.

• Mac: move Automations247 Computer to Applications. In System Settings → Privacy & Security, enable it in Accessibility and Screen & System Audio Recording (Screen Recording on some versions). Approve the Touch ID/password prompt on the Mac, then quit and reopen the worker. If an old enabled grant still reports denied after an app update, remove and re-add the installed app; reopen System Settings if its list is stale. Apple's permission instructions.
• Allow Automations247 Safe Storage if Keychain asks. Approve folder access when a task needs it; Full Disk Access is not a standard requirement.
• Windows: install the 64-bit worker for your normal user and keep Windows signed in and unlocked. Security prompts and the OS sign-in screen require someone at the PC.
• Power and startup: enable Start at login in the worker's menu bar/system tray menu. Keep the computer awake and online during work. Review Mac Battery → Options or Windows System → Power & battery for sleep settings. Closing the worker window leaves it running; quitting the app or sleeping the computer stops local execution.

Use your phone

1. Sign in to the mobile web app with the same account. Android has a testing app. Invited iPhone testers use the native TestFlight app; availability depends on Apple processing and beta review.
2. Go to Computers → Open computer. With worker 0.11.0 you can watch live while bots work. Bot browser has a separate saved profile. Full desktop shows existing apps and lets you choose the built-in or external monitor. Choose Take control when you want to click or type.
3. Pinch to zoom, drag to pan, tap the preview and type into Send to computer. Live frames retain your zoom and image during input. Finish takeover when done to resume computer actions. Protected OS prompts must be approved at the computer.
4. Notifications are optional. For iPhone web alerts, add the site to your Home Screen and enable notifications in Settings.

The phone manages your computer; it does not need a worker, database or Node.js, and it cannot control other phone apps. Both devices need internet access. Live viewing sends up to six image frames per second over HTTPS and has no audio. Frames are relayed in memory, excluded from task history and storage, and restricted to your authenticated account. The relay server can see frames in transit. Closing the view or signing out stops viewing, but an explicit takeover remains paused until you finish it.

What to keep on your computer

Keep the worker app, workspace files and signed-in browser/native-app profiles. The worker bundles its runtime and bot browser. Its private data is in ~/Library/Application Support/Automations247 on Mac and %APPDATA%\Automations247 on Windows. Back up these folders privately; do not share or clear them if you want to preserve pairing and sessions. Continue using the same operating-system user. Other apps keep their own sign-in data. Routines, bot records and encrypted API keys live on this server; they do not require a local database installation. Services may still expire a sign-in.

See the complete device checklist · Open Settings and check your computer

Install on another Mac or update your worker

Check Apple menu → About This Mac first. The current computer worker download supports Apple Silicon (M-series) Macs. On each Mac, move Automations247 Computer into Applications, open it, sign in to your own Automations247 account and pair that computer from Computers. Give the new computer a recognisable name so tasks use the intended machine.

For an update, finish any takeover and quit the worker on the computer you are updating, then replace the app in Applications. Keep its Application Support data so pairing, workspace files and browser sessions remain available. Grant Accessibility and Screen Recording to Automations247 Computer on each Mac. A change of app signing identity may require removing an old permission entry and adding the installed app again.

Apple verification and computer access are separate. Developer ID signing and Apple notarization make a direct download verifiable by macOS; they do not grant screen or keyboard permissions. The download card states the currently published signing status. If macOS says the developer cannot be verified or the app is damaged, stop and use the updated verified download when available; do not disable Gatekeeper. The TestFlight Mac app manages your team; the full computer worker must also be installed on every computer that will execute tasks.

Testing downloads

• Mac computer worker (Apple Silicon): availability and signing status
• Windows computer worker (64-bit)
• Android testing app

These are testing releases. The Mac download is offered only when a signed, notarized release receipt has been published; check the download card for availability. The Windows installer does not yet have a publisher signing certificate. iPhone and Mac management builds use TestFlight invitations once Apple makes them available.

Apps and computer access

The iOS, Android and TestFlight Mac clients manage your account. The full desktop worker executes approved files, terminal, browser and desktop actions. Phone apps do not control other phone apps. Native desktop control is optional and requires the platform's permissions. Workspaces share your computer user permissions; they are not virtual machines.

Keep using your signed-in apps

In Computers → Apps & sign-ins, save the app or browser profile you already use. Choose Full desktop to return to your regular browser and native apps. The bot browser uses its own persistent profile per workspace. Open the computer, check the intended account, then record your check. Bots read these directions before working. Passwords and browser cookies stay on the computer; services may still expire a login or ask for a security check.

Marketplace apps and skills

Open Marketplace → Apps & plugins. Choose Connect, sign in with your own service account in the browser, return and confirm the account for the selected company. Automations247 tests the connection and asks which bots may use it. If an account is already connected, choose Use instead of signing in again. In Yours, manage bot access, select allowed tools, pause or disconnect. Once you save a tool selection, newly discovered tools stay disabled until selected.

Skills contains original reusable workflows with visible instructions and required apps. Install into the selected company and choose bots. This does not grant service or computer permissions, schedule routines or run jobs. Your edited skills are preserved if installed again. Ask a bot to use the skill when ready. Connections, skill assignments and credentials are separate for each company. A bot can discover supported apps and offer a Connect card directly in chat, then continue its saved task after you choose an account.

On existing iPhone and iPad test builds, open Connections → Manage → Browse marketplace. Hosted marketplace and connector changes arrive when this view reloads; native menus and computer worker changes still require an app update. Supported catalog apps are Gmail, Google Calendar, Google Drive, Notion, Linear and GitHub. Other compatible public Streamable HTTP MCP services can be added with a server URL and optional bearer token. Connect services using your own accounts. Local executable plugins and community publishing are not available.

Google connections during beta

Google OAuth is in production, but branding and data-access verification are pending. Google may show an unverified-app warning and limits unapproved sensitive or restricted access to 100 users over the project’s lifetime. Automations247’s 500 free beta places do not remove Google’s separate restriction. Google must approve the requested scopes before unrestricted public access; restricted Gmail data may require a security assessment.

Automations247’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google data is used only for the connected features you request; it is not sold or used for advertising. Review connector access before granting it to a teammate.

Connect Gmail and other accounts

Select the company you want to work in. Open Connections and tap Connect beside Gmail, Calendar, Drive, Notion or Linear. Choose the required access, then Continue to sign in. GitHub uses a repository-scoped personal access token. Each connection belongs only to this selected company; other companies require their own connection and bot grants.

In the mobile or desktop app, tap the Sign in button shown directly in the connection panel. Google opens in Safari, Chrome or your system browser. After signing in, return to the app and confirm the service account and company shown there. This confirmation prevents a browser sign-in from silently connecting the wrong account. The sign-in link and unconfirmed result expire after ten minutes. Closing and reopening a pending connection in the same app session restores an available confirmation. Never paste passwords or verification codes into bot chat.

You can also connect directly from a task conversation. A bot that needs a service shows a Connect card. Once connected, choose the account and tap Use this account and continue task. This grants that bot access in the current company and resumes the original saved task; other action approval rules still apply. From the Connections page, choose which bots may use the account. You can pause, disconnect or remove bot access at any time.

On first opening the computer worker, missing desktop or Chrome requirements appear in a setup checklist. Computer access remains unavailable until its requirements are met. Mac Screen Recording and Accessibility must be approved on that Mac. Chrome extension tokens must be saved in Automations247 Computer on the assigned computer; the phone and management apps cannot store them on its behalf. Use a separate Chrome profile for each company to keep website sign-ins apart.

Company profiles separate hosted connections, bot grants, chats, tasks, routines, projects, memory and skills. Workspace files and Bot browser profiles have separate workspace folders. Your AI provider/key, billing usage and computer devices remain account-level. A company profile is an organizational boundary, not an operating-system sandbox: full-desktop and terminal access run as your computer user and can reach other local apps or files. Use separate OS users or computers when you need operating-system isolation.

If Google blocks a tester or shows an unverified-app restriction, the server owner must finish Google OAuth setup or add that Google account to the testing audience. Automations247 cannot bypass Google consent or verification. Refresh tokens in Google's Testing mode may expire after seven days.

Company and use-case profiles

Use the Company / use case switcher in the website or the company menu at the top of the native Apple app. Choose New company, name the company or use case, and describe its goals, responsibilities and recurring work. With your API key saved, Create my team with AI creates 1–5 teammates, each with distinct instructions and a first task. All teammates are saved together before work starts. A retry of the same creation request reuses its result. You can also create an empty profile and hire later. Edit the company brief from the profile menu, and change individual roles in bot chat.

Your existing work is kept under Personal. Switching profiles filters the team, conversations, task updates, routines, skills and memory; schedules continue for other companies even when they are not selected. Team tools enforce company boundaries on activity, task lookup and delegation. Shared memory means everyone in this company. To reuse a bot role in a different company, create a new teammate; existing conversations cannot be moved across company boundaries.

Profiles are organizational areas owned by the same signed-in user, not separate user logins or isolated operating systems. Your API key, model, daily token limit, connected accounts, paired computers and account-wide automation rules remain shared account settings. The account owner can manage all profiles. New teams have no service account, terminal, desktop or trusted automation grants; assign only the access they need. Full desktop and terminal permissions can reach the computer user's files and open apps, so do not treat these profiles as a sandbox for untrusted collaborators.

Choose a paired computer during creation or assign one in Settings later. Each company starts with its own workspace directory. My connected Chrome reuses the computer's existing Chrome extension connection, including the same signed-in profile. Company switching does not change Chrome users. Choose Separate Bot browser for a company-specific persistent browser session, or use a separate computer or OS login when stronger separation is needed. The computer must be awake and connected for local steps. Ordinary account sessions may still expire under the service's own rules.

Hiring, team updates and automatic work

Describe the job when hiring. Automations247 creates a first task from that request, so you do not have to repeat it. A coordinator can inspect actual teammate results, blockers and saved routines and delegate a report. Ongoing monitoring without a specified time uses a disclosed daily 9 AM check in your account timezone; change it in Routines or chat. The team updates feed contains results and questions with links to the task.

Reasoning, research and connected-service APIs can run on the server while your computer is offline or under takeover. Browser, desktop, terminal and local file steps wait for the awake paired computer and your permission to return control. No computer action runs on the hosting server. Assigned built-in Google read tools can run without repeated approval; writes and your saved Ask/Block rules still apply.

Automation rules

Tell a teammate, for example, “Create Gmail drafts automatically, but ask before sending.” It proposes saved rules for your review. Open Settings → Company → Approvals & automation rules to inspect, edit, pause or remove them. Block wins over Ask, and Ask wins over Automatic. Rules apply only to their selected tool calls and never grant new computer or connected-account access. An action already executing may finish. A Gmail API rule does not inspect mail sent through a browser or terminal; keep those tools on review when needed. Computer rules are not an operating-system sandbox.

Automations247 uses Google account data only for the user-facing tasks and features you request. Google data is not sold, used for advertising or used by Automations247 to train general-purpose AI models. Transfers to OpenAI are for your requested task features with your consent. Automations247’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Google setup and connected-data handling

The server owner configures the Google OAuth client in Administration → Connectors, using the Web application redirect URI https://automations247.com/oauth/callback. Users sign in with their own Google accounts; they do not need their own Google Cloud project. OAuth client secrets and service tokens are encrypted in the server vault. Requested service results can be retained in task history and sent through your selected AI provider; tokens are not placed in bot prompts. Disconnecting removes saved credentials and bot grants but does not undo completed service actions or delete earlier task history. To revoke the provider's grant too, remove Automations247 in that provider's account settings.

On older Apple management builds, open Connections → Manage to see and connect this company’s accounts in the updated settings. Older native summaries that cannot filter by company omit connection records to avoid mixing companies. The updated native list and task setup buttons require a new TestFlight build.

When a bot needs your computer

Open the task and choose Take control of computer (Open task computer in the Apple app). The task shows its assigned screen, where you can click, zoom and type. Choose I’m done to return control and continue that same task. You do not need to create a new task or repeat the original instructions. Closing the screen keeps computer control reserved. A sign-in request holds the computer while you respond; other bots can still use connected services.

The task keeps its saved browser and computer context. The bot inspects the current page after you finish, instead of repeating earlier clicks. Passwords and verification codes belong in the computer screen, not the bot conversation. If the screen cannot appear, check the permission guidance there: macOS Screen Recording and Accessibility must be granted on the computer itself. Your computer must remain awake and online.

Bot and computer permissions

Open Settings → Bot permissions on the website or Apple app, choose a teammate and enable its workspace browser or desktop access. You can also assign connected accounts there. In the Apple app, the same page is under the teammate’s About menu. These switches save immediately for that bot and company, and stay saved across tasks and app restarts. Browser access covers your selected Chrome or Bot browser. A disconnected computer or browser does not turn a saved grant off. Bots reuse existing grants; changing access through chat requires your approval. These switches do not grant macOS permissions or configure Chrome.

For signed-in Chrome, open Settings → Computer → Chrome connection in the separate Automations247 Computer worker on the paired Mac or Windows PC. Install Microsoft’s Playwright Extension in the intended Chrome profile, then save its token locally in the worker. If the save button is unavailable, choose the matching workspace and use Refresh Chrome setup status. The TestFlight Mac app is a management app, so it cannot save the worker’s token. On Mac, enable Automations247 Computer in Accessibility and Screen Recording. If a takeover is active, choose Finish takeover before bots can use the computer.

Gmail access can read, draft or send using the selected connector permissions. Deleting messages or blocking future senders currently requires the connected Chrome or full desktop. Enabling a bot’s computer access does not by itself delete mail.

Join iPhone or iPad testing

Open Join Automations247 on TestFlight on your iPhone or iPad. Install TestFlight if needed, join the beta, then install Automations247 and sign in. The free beta has 500 users in total. No separate invitation request is required; Apple shows whether a compatible build and a place are available. You can use the mobile website if testing is full or unavailable.

Earlier invitation requests remain visible to the owner. You can withdraw your saved request under Settings → App updates & testing; account deletion also removes it. Apple TestFlight membership is managed separately in TestFlight.

Use several computers with one account

Install and pair Automations247 Computer on each Mac or Windows PC. In Computers, assign each company workspace to its intended computer; its bots and routines use that assignment. The worker app identifies this computer and suggests it for a new team. Signing in from another computer or your phone does not move existing tasks. Independent computers can work at the same time within your account concurrency setting, while bots sharing a computer take turns for computer actions. Offline computer work waits for its assigned worker, without falling back to another PC. Configure OS permissions and Chrome profiles separately on each machine. Files and app sign-ins stay on that machine; they are not transferred by changing the assignment.

Continue in the same bot conversation

Your hired bot keeps its conversation and saved assignment. Temporary AI failures retry automatically twice, and longer work can continue through three additional run segments. Completed actions are retained. If your manager reports a blocked employee, choose Open employee’s task to see the exact conversation and any required input. After signing in on the assigned computer, select I’m done; the bot checks the current screen and continues the saved work. Sign-in, CAPTCHA, permissions, approvals, exhausted credits and uncertain actions can still require your attention. If automatic recovery is exhausted, Resume continues here. You do not need to create another conversation.

Install the testing apps

Download the Apple Silicon Mac worker, 64-bit Windows installer or signed Android APK from this website. Mac users should unzip and move Automations247 Computer to Applications before opening it. On Android 9 or later, open the downloaded APK and allow installation from the browser if prompted; that permission can be turned off after installation. Sign in with the same Automations247 account on your computer and phone. The Mac download card shows whether an Apple-notarized worker is available. The Windows testing installer does not yet have a publisher certificate. Use each computer’s own setup checklist; your phone cannot grant its initial OS permissions.

Inbox organization and calendar availability

In Gmail connection setup, Organize inbox enables archiving, returning selected messages to the inbox and user-label changes. It is off until you choose it and reconnect. Google’s modify permission also includes sending and trash access; Automations247 keeps sending tied to your separate access choice and exposes no trash or delete tool. Calendar availability checks require reconnecting older Calendar accounts. Task instructions and approval rules continue to apply. Reconnect / change access is also available in a task’s connection card.

Reuse WhatsApp Web

Save the intended Chrome profile in Connections → WhatsApp Web and choose the bots that may use it. The bot checks the open tabs exposed by that connection and selects WhatsApp without reloading an existing tab. It opens WhatsApp only when no matching tab is available. Existing sign-ins stay in that browser profile. The bot checks the actual page before continuing; it asks for linking only when the page requires it. It does not search other companies, computers or Chrome profiles for a login.

Business connections

Google Business Profile can read managed locations and reviews, draft replies in chat and optionally publish a reply with read-back verification. The server’s Google project needs Business Profile API approval and enabled APIs; a Google sign-in alone does not grant this approval. Google’s management scope includes write access, while Automations247 keeps publishing tied to your chosen connection access and task instructions.

Slack and HubSpot use your own registered OAuth application. Enter its client ID and secret in Connections, use the displayed callback URL, and authorize the intended provider account. Credentials are encrypted only for that company connection. Tools start disabled: choose the allowed tools, then the bots. Reconnecting resets those tool choices. Provider permissions, workspace approval, API quotas and subscription limits still apply; provider charges are separate from AI usage. Reusing one external provider account across companies shares that provider’s data and billing even though Automations247’s connections, chats and memories stay separate.

Apify scraping

Select your company, open Connections → Apify → Connect, and paste your own token from Apify API & Integrations. After verification, choose which bots may use it. Ask an assigned bot what data to collect, from which sites, and how many results you need. It can find a scraper, inspect its input and pricing, start a run, check progress and read paged results. Your usual approval settings apply.

Connections, bot access and saved task results stay in the selected company. Connect Apify separately in each company. Reusing the same Apify account shares its external storage and billing; use separate Apify accounts for separate provider data. Apify charges are separate from AI usage. Testing the connection does not run a scraper. Site restrictions, Actor permissions, provider limits and credits still apply. Requested data is processed by Apify and may be saved in the task and sent through your selected AI connection. No browser extension or local model is needed for this connector.

Employee inboxes

Connect AgentMail in Connections with your own inbox-scoped API key. The connection is saved only for the selected company; choose which bots may use it. Read-only access is the default. Draft access creates unsent drafts; sending needs send access and follows your task instructions and approval settings. Your AgentMail plan is separate from AI billing. Setup does not create an external account, invite anyone to another service or enable incoming-mail notifications. Connected mail requested by a task may be saved in that task and sent through your selected AI connection.

API usage and optional daily limit

Each registered account must supply its own OpenAI API key in Settings. Keys are encrypted in separate account storage. Hosted accounts never fall back to the server environment key or the primary owner’s key. AI hiring, tasks and routines wait for that account’s key; signup, downloads and TestFlight requests do not use an OpenAI key. In Settings, turn off Limit daily tokens and save to use your own API credits without a Automations247 daily stop. You can enable a numeric limit again later. Usage is kept and includes input, output, repeated context and team creation across all company profiles; the accounting day starts at midnight UTC. Tasks stopped by this optional limit resume automatically after you raise it above usage or turn it off. OpenAI billing, credits and request-rate limits remain separate; recharge or adjust limits in your OpenAI API dashboard when the provider requests it. Testing the saved connection checks key access and the model list, not your credit balance.

Free beta and later subscriptions

The first 500 account places are available for testing without a platform subscription. Existing active accounts count toward this cohort. AI credits, ChatGPT plan limits and third-party service charges remain yours. No card is collected or charged. When these places are filled, new registration pauses until paid subscriptions are available. Pricing and how the beta transitions to paid service will be announced before payment is requested.

The owner can see the number of allocated beta places. Your account is recorded as a beta participant. Deleting an account removes its enrollment link; an anonymous used-place count remains so deleted accounts do not recycle the promotion.

Data handling during testing

Account email, password hash, sessions, bots, task conversations, memories, routines, company contacts and interaction history, saved app names, starting addresses, account labels, sign-in directions, confirmation times and usage records are stored on the Automations247 server. Each account has a separate database and vault key. OpenAI API keys and connection tokens are encrypted there. The owner-only admin panel shows user emails, task titles and statuses, routine names and schedules, computer connection status and API token usage. It does not display task conversations, files, screenshots, API keys or connection tokens. Server administrators can access hosted records and vault keys outside this panel. Successful sign-ins, registrations, owner views of user summaries and deployments are recorded in the admin activity log; the latest 10,000 activity events are retained. Sign-in tracking starts with version 0.4.0. Deployment history is retained.

When a task runs, its instructions, workspace sign-in directions, selected memories, tool results and requested images or screenshots are sent to OpenAI. Assigned third-party MCP services receive their tool arguments. Workspace files and authenticated browser profiles stay on the connected computer unless their contents are requested for a task or downloaded through the dashboard.

There are no advertising SDKs or advertising tracking identifiers in these apps. Notifications use generic task-update text. Devices retain login cookies and private application data to keep you signed in; full workers protect pairing credentials using operating-system storage.

Delete or recover an account

Use Settings → Delete account to revoke devices and remove active hosted records, API keys and administrative activity tied to your account. Local files and browser profiles remain on your computer. Earlier server backups expire through the seven-copy backup rotation; these backups are on the same server, not an offsite copy. A task already executed on an external service cannot be undone by deleting an account.

For account recovery, deletion help or testing support, contact praveen.lvnp@gmail.com. Do not send passwords or API keys.

Last updated September 12, 2026.

Versions and updates

Open Settings → Updates to see each computer’s installed worker version, current downloads and what changed. Computers and update-blocked task cards link to the same screen. The dashboard version is separate from Automations247 Computer.

On the computer being updated, finish manual control and let active work finish. Quit Automations247 Computer from its menu bar or system tray. Mac: download the Apple silicon ZIP, unzip it and replace Automations247 Computer in Applications, then reopen it. Windows: run the current x64 installer and reopen the app. Existing pairing and Chrome profiles stay in the user’s application data. Check that the same computer reports the new version and reconnects. Updating one computer does not update your other computers.

The Mac download is for Apple silicon. The Windows download is currently an unsigned testing installer. Native iPhone/iPad and Mac management app changes arrive through TestFlight; controller improvements and hosted dashboard updates do not replace those native binaries.

Chrome after a restart

Sign in to your computer after restarting and keep Start at login enabled in the Automations247 Computer menu. Saved Chrome profiles reconnect automatically while the computer is idle. The original profile and website sign-ins remain on that computer. No new Bot browser is created. Recovery waits while you have computer control and never repeats an interrupted click, message or form submission. If a site signs you out or asks for human verification, complete that step in the same Chrome profile.

Sign in to your Mac from your phone

Mac sign-in testing uses macOS Screen Sharing with a separate owner-only connection. Install the current worker, enable System Settings → General → Sharing → Screen Sharing for only your Mac user, then enable Allow remote Mac sign-in in the Automations247 Computer menu bar icon. Keep the worker running and the Mac awake. Open a task’s Full desktop takeover and choose Sign in to Mac / setup. Enter your Mac credentials there, outside bot chat. Once you see the same desktop, disconnect, refresh the task’s screen and choose I’m done.

Automations247 does not save this connection’s passwords or byte traffic to tasks or command history, and does not automatically retry credentials. Screen Sharing opens a local network service; do not open router ports or enable the shared VNC password. This feature still needs physical lock-screen verification. It does not support logout, restart, FileVault startup or Windows sign-in. Apple’s setup instructions.

Copy a selected file to another computer

In Files, choose Copy to another computer, select a workspace in the same company, then review the file and destination before confirming. Documents and images up to 8 MB are supported. Both computer apps need verified-transfer support. Prepared bytes are encrypted on the server for up to 24 hours, with at most five pending transfers per account. The destination verifies the reviewed hash before marking the copy complete. Retries check the same path; they do not create extra copies or overwrite different files. Browser profiles, credentials and bot assignments are not transferred. Cancelling cannot remove a file already copied. Account exports include transfer metadata; account deletion removes server transfer records and prepared bytes, while files already copied stay on their computers.

Sharing with people

Project owners can publish a separate text copy and invite signed-in people by email to view or comment. Only explicitly published material and human comments are shared; comments show the author’s email. Guests cannot access bot conversations, files, credentials, computers or tasks, and comments never enter bot execution queues. Revoking membership stops further access but cannot erase copies already seen or downloaded. Owners can remove the shared copy; account deletion removes owned copies, memberships and authored comments. Export shared data from Projects for the selected company.

External packages

Marketplace accepts Automations247 plugin JSON files up to 500 KB. Review the declared publisher, source, license, all instructions and changes before installing. Publisher details and requested access are declarations, not verification. Versions remain pinned until you review another upload. The last five versions are available for review and rollback. Local skill edits require separate replacement confirmation. Packages cannot install scripts or credentials, grant computer access, start work or enable service tools. Add a paused service, then connect your own account and select allowed tools. Employee templates import as independent copies with paused routines. Disabling a package detaches its managed skills and pauses linked routines; existing employee copies and connected services are kept.

Optional diagnostic reports

From a failed or blocked task, choose Report a problem. Create a private preview and inspect every field before sharing. The server owner receives only the account email, request/task/company IDs, general issue category, task state, component versions and timestamps shown in that preview. Raw errors, prompts, conversations, screenshots, files and credentials are excluded. Versions describe the current capture, not a reconstruction of earlier failure. A failed submission keeps the private draft, and retrying the same report does not create duplicates. Withdraw and delete removes the shared report and its draft; account deletion removes all diagnostic records and associated administrative activity. Up to 100 drafts and their linked reports are retained per account.

Document previews and search

Open PDF, Word DOCX and Excel XLSX files up to 8 MB in Files. Hosted previews run locally in your browser without AI calls; layout and text extraction have limits shown in the viewer. The Apple app uses its native document viewer. Original files remain on their assigned computer. Saving searchable preview text is optional: up to 100,000 characters per file are stored privately for that company on the server. Remove this cache from Files at any time. It is not a backup or a verified live copy. Account deletion removes saved search text.

Company setup and API billing

New companies are saved before AI team design starts. If your API key, provider credits or model prevents team creation, your company brief stays saved and the team page offers Retry team setup. A successful retry creates that company’s workers and first tasks once. OpenAI API credits are separate from a ChatGPT subscription and Automations247’s optional daily token limit.