Save Workflow Results to the Journal

Save Workflow Results to the Journal

A workflow can save its result to the Feluda Journal.

This is useful when the output should remain available after the run ends.

Instead of reviewing the result only in RunFlows, you can keep a structured Journal entry that is easier to browse, compare, and return to later.

Common examples include:

• meeting summaries;
• project updates;
• research findings;
• recurring reports;
• monitoring results;
• review notes; and
• decision records.

Test the Journal action manually before using it in a recurring or scheduled workflow.

What the workflow needs

A Journal-writing workflow normally needs:

• source information;
• one or more processing steps;
• a clear title;
• structured entry content;
• access to the Journal tool; and
• an output or confirmation step.

A simple structure might look like:

Input
→ Prepare Journal Content
→ Write Journal Entry
→ Output

The exact blocks depend on how your workflow is designed.

Start with a tested workflow

Before adding the Journal action, confirm that the workflow already produces a useful result.

Test whether it:

• receives the correct input;
• uses the intended provider and model;
• follows the required path;
• returns a clear structure;
• handles missing information;
• avoids unsupported claims; and
• completes without hidden errors.

It is easier to troubleshoot the Journal step when the earlier workflow steps already work.

Decide what should be saved

Do not save every intermediate message automatically.

Choose the information that will remain useful later.

For example, a meeting workflow may save:

• a short summary;
• decisions;
• action items;
• owners;
• deadlines; and
• unanswered questions.

A research workflow may save:

• the topic;
• key findings;
• source references;
• uncertainty;
• follow-up questions; and
• recommended next steps.

Keep the entry focused on one purpose.

Choose a clear entry title

The title should explain what the entry contains.

Useful titles include:

• Meeting Summary — 2026-06-08;
• Weekly Project Review — 2026-W23;
• Customer Interview Findings — North Region;
• Research Brief — Local AI Models; or
• Daily Operations Report — 2026-06-08.

Avoid titles such as:

• Report;
• Entry;
• Result;
• Workflow Output; or
• Final.

Clear titles make the Journal easier to browse.

Add dates to recurring entries

A recurring workflow should create distinguishable titles.

Include a:

• date;
• week;
• month;
• project;
• region;
• customer; or
• reporting period.

For example:

Weekly Support Review — 2026-W23

is clearer than:

Weekly Support Review

Dated titles also make duplicates easier to identify.

Use a consistent entry structure

Repeated Journal entries should follow the same structure.

For example:

# Weekly Project Review

## Summary

[Short overview]

## Completed Work

* [Item]

## Current Blockers

* [Item]

## Upcoming Deadlines

| Owner | Task | Deadline |
|---|---|---|

## Decisions Needed

* [Decision]

## Unanswered Questions

* [Question]

Consistent entries are easier to compare over time.

Prepare the Journal content

Use an AI step to prepare the final entry content before the write action.

A useful instruction could be:

Read the workflow input and prepare a Journal entry.

Return:
1. a summary of no more than 100 words;
2. a list of decisions;
3. a table with Owner, Action, and Deadline;
4. current blockers; and
5. unanswered questions.

Use only the provided information.
If a detail is missing, write "Not provided."
Do not guess.

Test this instruction in Workbench before adding it to the workflow.

Keep facts and suggestions separate

When the entry includes both source facts and AI recommendations, separate them clearly.

For example:

## Confirmed Findings

[Facts from the source]

## Suggested Next Steps

[Suggestions for human review]

Do not present recommendations as confirmed decisions.

Make missing information visible

A Journal entry should show when information is unavailable.

Use a value such as:

Not provided

instead of leaving the field empty or allowing the model to guess.

For example:

Owner	Action	Deadline
Mia	Confirm interview dates	Not provided

This makes the entry easier to trust and review.

Add the Journal action

Add the step that writes the prepared content to the Journal.

Depending on your Feluda setup, this may use a Journal tool made available to an LLM or another supported workflow action.

Configure the step with:

• the intended journal or destination;
• the entry title;
• the prepared content;
• any required settings; and
• the correct tool permissions.

Keep the write step focused on saving the completed entry.

Use a direct write instruction

When an LLM controls the Journal tool, make the action explicit.

For example:

Use the enabled Journal tool to create a new entry.

Title:
Weekly Project Review — 2026-W23

Content:
[Prepared Journal content]

Create the entry in the selected Journal.
Do not only display the content in the workflow output.

This helps distinguish between drafting the entry and performing the write action.

Confirm the Journal tool is available

Before testing the workflow, confirm that:

• the Journal tool is available;
• the relevant Gene or built-in capability is active;
• required settings are complete;
• the selected model supports the required tool use; and
• the workflow step has access to the tool.

Test the tool in Workbench when you are unsure whether the problem is the tool or the workflow.

Add a final confirmation output

The workflow should return a clear result after the Journal action.

For example:

Journal entry created:
Weekly Project Review — 2026-W23

Or, when the action fails:

The Journal entry could not be created.
Review the workflow activity and Journal tool settings.

A visible confirmation makes the run easier to review.

Do not treat the confirmation as proof that the saved content is correct.

Test with non-sensitive information

Use a simple sample before using real project or customer data.

Confirm that:

• the correct title is used;
• the complete content is written;
• Markdown displays correctly;
• missing values remain visible;
• the workflow reaches the Journal step;
• the entry appears in the Journal; and
• no duplicate is created.

Open the Journal after every important test.

Confirm the write action

After running the workflow:

1. review the RunFlows output;
2. check the tool or activity result;
3. open the Journal;
4. find the expected entry;
5. review its title;
6. review its content; and
7. compare important facts with the source.

A successful tool call confirms that something was written.

It does not confirm that the content is accurate.

Review Markdown formatting

Check whether:

• headings appear correctly;
• bullet lists are readable;
• tables contain the right columns;
• links work;
• code blocks are closed correctly; and
• long sections remain easy to scan.

Simplify the structure when formatting makes the entry harder to read.

Prevent duplicate entries

Duplicates may appear when:

• the workflow runs twice;
• a timeout is retried;
• a schedule overlaps;
• the title never changes;
• two workflows write to the same Journal; or
• a manual and scheduled run create the same report.

Reduce duplicates by:

• using unique or dated titles;
• checking the Journal before retrying;
• reviewing active runs;
• preventing overlapping schedules;
• confirming whether a delayed write already completed; and
• removing duplicate schedule configurations.

Handle a timeout safely

A timeout does not always mean the Journal write failed.

Before running the workflow again:

1. open the Journal;
2. search or browse for the expected title;
3. compare timestamps;
4. review the workflow activity;
5. confirm whether the entry exists; and
6. retry only when the first action did not complete.

This prevents duplicate entries.

Handle a missing entry

When the expected entry does not appear, check:

• whether the workflow ran;
• whether earlier steps completed;
• whether the Journal tool was called;
• whether the correct destination was selected;
• whether the title was different;
• whether the tool returned an error;
• whether permissions blocked the action; and
• whether the workflow stopped before the write step.

Find the first failing step before repeating the run.

Handle the wrong entry title

A wrong title may come from:

• a fixed title that was not updated;
• a missing date;
• incorrect information passed from an earlier step;
• the wrong workflow version;
• an unclear title instruction; or
• a schedule that still uses old input.

Keep the title creation simple and test it separately.

For recurring reports, use a consistent date format.

Handle incomplete content

If the entry is created but information is missing, review:

• the source input;
• the AI instruction;
• intermediate extraction;
• output length limits;
• the selected model;
• missing-value rules; and
• whether the full result reached the write step.

Find the earliest point where the content became incomplete.

Handle incorrect content

Compare the saved entry with the source.

Look for:

• changed names;
• incorrect dates;
• invented deadlines;
• missing decisions;
• unsupported claims;
• suggestions presented as facts; and
• information placed under the wrong heading.

Improve the content-preparation step before changing the Journal write step.

Use the Journal with scheduled workflows

A tested Journal workflow can be scheduled.

For example, a weekly workflow may:

1. collect approved source information;
2. prepare the weekly review;
3. create a dated Journal entry; and
4. return a completion result.

Before scheduling it, confirm:

• the source will be available;
• the title changes for each run;
• the Journal tool works;
• duplicate output is controlled;
• the normal runtime is understood;
• errors remain visible; and
• someone reviews the new entry.

Use Journal Monitor

Journal Monitor can help you watch for new entries from a running or scheduled workflow.

Open the monitor and select the journal you want to observe.

When a new entry appears:

• confirm the title;
• confirm the timestamp;
• open the full entry;
• review the content;
• compare it with the source;
• check for duplicates; and
• decide whether follow-up is needed.

Journal Monitor shows new activity.

It does not approve the result.

Organise workflow-created entries

Use consistent naming for related results.

For example:

• Research — Daily Findings — 2026-06-08;
• Support — Weekly Review — 2026-W23;
• Project Atlas — Monthly Summary — June 2026.

A consistent pattern makes entries easier to sort and compare.

Add source information

Include a source section when later verification may be needed.

For example:

## Source

* Workflow: Prepare Weekly Project Review
* Reporting period: 1–7 June 2026
* Source file: project-status.md

Use source links, filenames, dates, or workflow names that help the reviewer understand where the entry came from.

Add a review status

When the entry needs approval, include a visible status.

For example:

**Status:** Needs Review

Other useful values may include:

• Draft;
• Approved;
• Superseded; or
• Archived.

Use a status only when someone is responsible for reviewing and changing it.

Keep historical corrections visible

When an entry acts as a record, avoid silently replacing earlier facts.

Add an update section instead.

For example:

## Update — 2026-06-10

The launch date was later confirmed as 20 June 2026.

This preserves the original context and the later correction.

Protect sensitive information

Before saving sensitive workflow output, check:

• whether every detail is necessary;
• whether personal information can be removed;
• which model processed the content;
• whether a cloud provider received it;
• which tools were used;
• whether the correct Journal was selected; and
• who can access the computer and user account.

Never write API keys, passwords, access tokens, or other credentials to the Journal.

Use the intended Secrets or provider settings instead.

Keep a human reviewer

Human review is especially important when Journal entries affect:

• customers;
• employees;
• money;
• contracts;
• legal rights;
• health;
• safety;
• security; or
• access to important services.

A workflow can create a useful record.

It should not turn an unreviewed AI result into an approved decision.

A practical Journal workflow

A simple workflow might look like:

Input
→ Prepare Structured Summary
→ Write Journal Entry
→ Return Confirmation

Test it with:

• normal input;
• missing information;
• long input;
• unusual formatting;
• a Journal tool error;
• a timeout; and
• a repeated run.

Confirm the saved result after every test.

Final checklist

Before relying on a Journal-writing workflow, confirm that:

• the workflow result is useful;
• the entry title is clear;
• recurring titles include a date or period;
• the content uses a consistent structure;
• missing information is visible;
• facts and suggestions are separated;
• the Journal tool is available;
• the write action has been tested;
• the destination is correct;
• duplicate prevention is in place;
• errors remain visible; and
• someone reviews the saved entry.

Saving a workflow result to the Journal turns temporary output into a reviewable record.