Job Quickstart

This guide gets one useful Job into your dashboard. You will choose how it starts, add work steps with explicit behavior and tone where needed, attach safe capabilities, add an output when needed, and check the run.

Open the TROPIKAL workspace and sign in with your TROPIKAL ID.

The setup model is job-first:

The job owns the job.
AI behavior belongs in versioned work-step instructions.
Functions and capabilities are approved actions.
Accesses are connected accounts that functions may use.
Runs show job execution status, step progress, review pauses, and safe outcomes.

2. Create the job

Click New job. The job opens as a canvas with one Trigger node in the middle.

Choose one trigger type:

Trigger	Use it when
Channel	The job starts from a supported customer-Job channel such as email or Telegram.
Schedule	The job runs on a recurring cadence.
Manual	An owner starts the job from the job detail page.

Channel shows the supported customer-Job channels. Website Chat is configured separately as a Website Component; it is never created from this Job canvas. Schedule cadence, time, and timezone stay inline in the Trigger node.

Then add the job shape:

Configure the Trigger.
Add Work Steps for the work the job should perform.
Add Output for owner review, handoff, draft, or save/publish destinations.

Channel and output setup belongs on the Job canvas. AI tone, style, and decision guidance belong directly in the relevant work step.

Work Steps have three setup choices:

Work Step	Use it when
Prompt	An AI step should read the work so far and write a drafted or analyzed result.
Capability	An approved function or Connected Data action should run.
Condition	The job should choose a path from workload fields.

The job carries the work forward from step to step. Prompt and Capability steps write useful results, and Output sends the final result to a handoff, review, saved draft, email attachment, or Website publish destination.

Use a focused job as the starting point:

Template	Use it when
Receptionist & Booking	The job should answer initial questions, collect booking details, and route the request for follow-up.
Customer Support	The job should answer product or service questions from approved material.
Lead Qualifier	The job should collect contact details, service interest, urgency, and preferred time.
Knowledge Base	The job should answer from documents, URLs, or site content.

After saving, open the job detail page. The slug becomes the stable handle used in dashboard routes, install snippets, and API paths.

3. Write AI work-step instructions

For each AI step, write the task, tone, role, decision boundaries, and escalation rules that the immutable Job version must preserve.

You are the front desk assistant for Acme Clinic.
Answer in a calm, concise tone.
Ask for a name and phone number before booking.
If you do not know an answer, say what information is missing.
Never invent prices, policies, or appointment availability.

Put factual reference material in Knowledge instead of pasting it into step instructions. Put actions and integrations in Functions or Capabilities.

A Job does not need an AI step when it only runs functions, moves structured work forward, saves a review item, sends a notification, or publishes already reviewed content.

4. Chat-test the job

Open the chat panel and ask three first questions:

A normal question the job should answer.
A question outside scope.
A request that should trigger a next action, such as checking a resource or collecting lead details.

Adjust the work-step instructions until the Job handles all three predictably.

5. Add knowledge

Create a knowledge source when the job needs reliable information from docs, policies, FAQs, pages, or approved copy. Link the source to the job, then ask a question whose answer appears only in that source.

Good knowledge sources are specific and current. Split unrelated policies into separate entries so you can update or remove them independently.

6. Add functions and capability steps

Use Capability work steps when the job must act outside a normal text response. Common first capabilities include:

Capability shape	Example use
Read-only HTTP function	Look up order status, appointment slots, or public catalog data.
Connected account function	Read approved records from an account such as Drive, Calendar, or bexio.
Create/update function	Save a lead, create a draft, or update a CRM record after confirmation.
Connected Data	Read approved site content, create a draft, or publish reviewed content.

If a capability needs an account, choose an existing Access. For example, a Google Drive or bexio function should use the matching Access. If no matching Access exists, add it from the setup flow; after connection, return to the job editor and continue configuring the same step.

Start read-only. Add write or publish actions after the read path is proven and the job has the right review step.

7. Add inputs and outputs only when useful

Telegram, email, Calendar, Drive, and other Job integrations should be connected only when the Job needs them. Each input or output expands what the Job can see or do, so test again after enabling it.

Use the Trigger node with Channel when you want the Job to start from a supported channel such as email or Telegram. Use the Output node for an owner handoff, review artifact, draft, email attachment, or Website publish destination.

Use the Website Chat Component when you want a floating AI Front Desk bubble on a public Website. An owner may explicitly add selected customer Jobs as tools for that Component.

Use the Calendar Booking Component when a connected Website should show real Google Calendar availability and confirm a selected slot. It is managed from the Website, not from Jobs.

For public AI Front Desk jobs, confirm that Runs and owner handoffs show a safe receipt: what was answered, what was qualified, what booking or follow-up request was created, and what the owner should review next.

8. Troubleshoot the first run

Symptom	First check
Job answers too generally	Add knowledge and ask a question that requires the source.
Job ignores instructions	Tighten the work-step instructions and remove conflicting instructions from old knowledge.
Capability does not run	Confirm the function is linked to the job and the user request clearly needs that capability.
Capability needs an account	Open Accesses, reconnect the account if needed, and confirm the Job is allowed to use it.
Knowledge answer is missing	Reprocess the knowledge source and verify it is active for this job.
Connected Data is denied	Check that the website is connected, synced, and allowed to use that action.
Website publish is not available	Connect and sync the website, then confirm a publish action is ready.
Lead is incomplete	Ask for the missing contact, service, or timing detail before handoff.

Open Runs to check live progress. The overview shows the current step, and the detail view shows each planned step, completed outputs where safe, failed step errors after redaction, and review links when a job pauses for approval.

Next: create a focused job in Create your first job, learn how to manage Accesses, add Website Calendar Booking, or learn how to publish to a website from a job.