Set Up Your First Job

A Job turns a goal into a teammate. You describe what you want, answer a short wizard, and from then on Hubi handles that work on its own. Here is the full walkthrough.

1. Describe the Job

Open the home dashboard and go to the Jobs tab. In the box that asks "What job should Hubi take care of?", describe the outcome in plain language:

"Run our weekly competitor recap - every Monday, summarize what our top three competitors shipped and post it for the team."

Hubi drafts the job while you watch: a title, the goal, the integrations it will need, and a starter skill. Then the wizard opens.

Already had the conversation? If you have been discussing this work with Hubi in a chat, use Make it a job there instead. The meter above the composer tells you when the conversation describes the work well enough, and Hubi asks for whatever is still missing.

2. Confirm the Goal

The first step shows what Hubi understood: what the job does on every run, and the integrations it relies on. Read it, fix anything that is off, and continue.

3. Choose How Results Arrive

Slack or Email. Pick Slack if the team should see the output and be able to reply to it in-thread. Pick Email if it is a report for you.

4. Connect What It Needs

Hubi lists the apps this job suggested - Google, HubSpot, Search Console, whatever it will use. Connect them here, or skip and add them later from Capabilities > Integrations.

5. Give Hubi Its Instructions

The Create skill step is where the job learns how to do the work. Chat it through with Hubi, or start from a template's instructions if you picked one. Be specific about the output you want: format, length, tone, what to leave out.

6. Say Where Hubi Works

Pick the Slack channel Hubi will post in, then invite @Hubi to that channel in Slack so it can post there.

7. Add Knowledge (Optional)

Point the job at Brain folders or files it should read from on every run - brand guidelines, examples, a competitor list. Anything the job needs to sound like you belongs here.

8. Set the Schedule

Choose how often: only on request, monthly, weekly, weekends, daily, or as often as every 10 minutes. Daily and slower cadences also let you set the time of day.

9. Test It

Hubi runs the job once and delivers the result through the channel you picked. This is the real thing, not a preview - read it, and go back and sharpen the skill if the output is not what you wanted.

10. Activate

Activate the job and it starts running on its schedule. It moves from Needs setup to Active, and Hubi takes it from there.

Tips

• Start narrow. One clear outcome per job works better than a vague catch-all.
• Feed the folder. Drop brand guidelines, examples, or reference docs into the job's Brain folder so Hubi has context on every run.
• Iterate in the channel. Reply in-thread to refine Hubi's output, just like working with a teammate. Changes you agree on there can be folded back into the skill.
• Test before you activate. The test run costs one run and saves you a month of wrong reports.

For more channel-based workflows, see Manage Your Company at Slack.