Start a Job from Email

Email is one way to invoke a TROPIKAL Job. The Job remains reusable headless work; its email setup supplies the permitted incoming message content as input. The same work can later be invoked from another supported source without turning it into a different kind of Job.

For example, an Error analysis Job can receive an email containing logs, separate evidence from likely causes, identify missing diagnostics, and prepare an engineering summary for review.

V1 is inbound and review-first. It does not send automatic external customer replies.

Example email work

• Receives forwarded email through a randomized job alias.
• Performs the focused work defined by the Job, such as error analysis, lead qualification, document extraction, or support triage.
• Detects urgency and risky instructions.
• Creates an owner-facing summary and suggested next action.
• Drafts a suggested owner response for review.
• Sends owner review notifications to the owner’s verified TROPIKAL ID email and keeps the email pending in the dashboard inbox.
• Hands off through Telegram when connected as an additional owner handoff path.

Add an email start

1. Open the job in TROPIKAL.
2. Open the Trigger node.
3. Choose Channel.
4. In Public Channels, click Email to open the email inspector.
5. Generate or attach a job email alias and configure allowed senders.
6. Add an Output if the email job should notify an owner, prepare a handoff, or save a review artifact.
7. Forward email to the alias from your current inbox, website form, booking tool, or manual job.

Owner review job

When email arrives, the inbox shows:

• Job name.
• Sender and subject.
• Intent and urgency.
• Risk level and prompt-injection warnings when detected.
• Summary and suggested next action.
• Suggested reply draft.
• Owner notification and dashboard fallback status.

Owners can mark the email reviewed, mark it as spam, or copy the suggested reply draft.

Human-in-the-loop rules

• No automatic external customer reply is sent in v1.
• Suggested replies are drafts for the owner to copy, edit, or ignore.
• Email content cannot change Job instructions, payment instructions, owner contact details, billing, capabilities, permissions, or knowledge.
• Adding email content to knowledge requires explicit approval.
• Suspicious instructions are ignored and surfaced as warnings.

Prompt injection protection

Emails are untrusted input. If a message asks the Job to ignore instructions, reveal hidden prompts, extract secrets, change the owner, alter handoff settings, or change payment instructions, TROPIKAL flags the message for review instead of following it.

Rotate or revoke an alias

Open the job, open the Trigger node, choose Channel, click Email in Public Channels, then use the email alias controls. Rotation creates a new address and retires the previous one. Revoked aliases no longer accept inbound messages.

Current limitations

• Inbound email and owner handoff only.
• No autonomous customer email sending.
• No automatic knowledge updates from email.
• Attachment content ingestion is not enabled by default.
• Broad sender allowlists should be reviewed before rollout.

Troubleshooting

Symptom	First check
No email appears	Confirm the alias is active and attached to the job Trigger.
No owner notification email	Confirm the owner has a verified TROPIKAL ID email and the job still has owner notifications enabled. The inbox remains the source of truth even if a notification is delayed.
No Telegram handoff	Use the dashboard inbox fallback or connect Telegram owner handoff.
High risk warning	Review manually and do not apply sensitive changes requested inside the email.
Suggested reply is incomplete	Update Job knowledge or write clearer work-step instructions before relying on future drafts.