Finishing connection

Sending the result back to your Hub.

Working...
motaai.cloud
MMMota Media Client
Slack pending

Mota Media Client

One step left. Finish setup and we deploy your AI employee.

SlackPendingConnect workspace
Active jobs0Jarvis workflows
Connected tools0Available to Jarvis
Scheduled tasks0Active schedules
J
JarvisConnect your Slack workspace
Setup needed

Jarvis will work in any channel where your team adds and mentions it.

Workspace readiness0 / 3
1

Connect Slack

Authorize the workspace where Jarvis will work.

Now
Slack workspace not connected

System status

Live workspace health.

Checking operations

Verifying routes, runtime, jobs, and approvals.

Jarvis online—
Slack active—
Issues—

Profile summary

Business context for Jarvis.

NameNot saved
IndustryNot saved
Services
Not saved
Customers
Not saved
Voice
Not saved
Language
English / French
Notes
Not saved
Client profile

Business profile

This context is sent with every job your AI employee runs.

1Business identity

2Audience & voice

✓ Saved Changes apply to every future AI job.
Slack setup

Connect Slack

Authorize the workspace once. Jarvis works in any channel where your team adds and mentions it.

Slack

Not connected yetPending

Connect with your Google account, then authorize Slack. One click.

Slack access — workspace level

After connecting, add Jarvis inside Slack wherever you want to use it. Hub disconnect will not remove Jarvis from those channels.
No channel setup here.

Your Slack admin controls where Jarvis is added. Disconnect only removes the Hub link; Slack channel access stays in Slack.

AI Employees

Hire an AI employee

Activate a ready-made job for Jarvis.

Request 1-on-1

Need a custom employee?

Tell us the job, tools, and Slack flow. We’ll build it with you.

Request 1-on-1
Tasks

Tasks

Create a task here, or by talking to Jarvis in Slack.

Connect tools

Integrations

Connect other approved tools your AI employee can use. Slack is handled in Slack setup.

Credentials stay encrypted and controlled.

Supported OAuth brokers are reviewed per connector before production use. API keys submitted here are encrypted with AES-GCM using the Hub token-encryption secret, scoped to this workspace, and never returned after save.

✓