Job Quickstart

This guide gets one useful Job into your workspace. A Job is reusable, headless work: it accepts input, performs configured steps, and returns an outcome. It does not own a visitor interface or Component UI.

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

The setup model is job-first:

The Job owns reusable work, not a customer-facing experience.
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. Name the outcome, not the channel or interface. Good names include Analyze incoming errors, Qualify a lead, and Prepare daily operations brief.

Choose how the Job starts:

Start	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.

Email, Telegram, schedules, and manual starts are ways to invoke the same kind of Job. They are not different Job archetypes. Website Chat is configured separately as a Website Component; it is never created from Job setup.

Then add the job shape:

Configure how the Job starts.
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 focused work as the starting point:

Example Job	Use it when
Error analysis	Email, Telegram, or another approved source supplies logs or an error report that needs a likely-cause summary.
Lead qualification	A message or form supplies lead details that need research, scoring, and a next action.
Invoice extraction	A document needs structured fields, total validation, and owner review.
Daily operations brief	A schedule should collect approved work summaries and prepare one concise brief.
Customer follow-up	An incoming request needs a draft response and approval before delivery.

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.

Analyze the supplied application error for the engineering owner.
Separate observed evidence from likely causes.
Ask for the missing timestamp, request ID, or logs when the evidence is incomplete.
Never invent events that are not present in the input or approved Knowledge.
Return a concise incident summary, likely causes, and the safest next check.

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. Test the Job

Run three representative inputs from the configured start:

A normal input the Job should complete.
An incomplete input that should request or report missing information.
A hostile or out-of-scope input that must not change Job instructions.

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 an interactive visitor chat on a public Website. An owner may explicitly add selected customer Jobs as tools for that Component. The Component owns the conversation; each selected Job remains headless background work.

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 Jobs that accept public input through an approved Component, confirm that the run history and owner handoffs show a safe receipt: what was analyzed or qualified, what follow-up was prepared, 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 the Job’s run history to check 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.