Skip to main content
Gratona

Journeys and automation

Turn fundraising signals into assigned work.

Create follow-up when a gift, lapse, event, sponsorship, trip, or relationship change calls for action. Gratona keeps the trigger, owner, due date, review state, and result on the same record.

System automations are included on Launch. Configurable Journeys begin with Growth; cross-program automation and advanced approvals begin with Scale.

Compare plans

Clear ownership

Every task has an owner, due date, source record, and status, so staff can see which donor work is waiting and why.

Repeatable follow-up

Use Journeys for work that should happen consistently after gifts, event activity, missed commitments, or other defined signals.

Review where it matters

Put donor-facing, financial, or sensitive work through the approval queue required by the program and plan.

From signal to completed work

The workflow starts with a supported record change. Its enrollment records progress to completion or exit, while steps that create tasks, reviews, or activity retain their own results.

  1. Step 1

    Choose the trigger

    Use a supported change in donor, gift, campaign, event, sponsorship, trip, task, or engagement data to start work.

  2. Step 2

    Apply conditions

    Limit the Journey to the right program, segment, relationship state, amount, date, or other supported record criteria.

  3. Step 3

    Assign steps and review

    Create tasks, communication work, waits, decisions, and approvals with named owners and visible status.

  4. Step 4

    Measure the result

    See which steps finished, where work stopped, and what changed on the donor or program record.

Product record

Inspect the enrollment and the work its steps create.

Every Journey enrollment retains its related record, current step, status, and timing. Owners, due dates, reviews, and recorded activities appear when the configured step creates those records.

Enrollment

Journey, related record, and current step

The enrollment connects the Journey to the donor, program, or other supported record that entered it.

Progress

Active, paused, completed, or exited status with timestamps

Entered and completed timestamps, current step, and any exit reason show where the enrollment stands.

Step-dependent work

Task owner, due date, review state, or recorded activity when configured

These fields belong to the task, approval, communication, or activity created by a step; they are not universal enrollment fields.

Ask to trigger a supported Journey in a test record, inspect its enrollment, then verify the additional task, review, or activity fields created by each configured step.

Choose the plan by workflow scope

  • Launch includes system automations needed for the connected CRM and selected primary workflow.
  • Growth is the entry point for configurable core Journeys across a growing development operation.
  • Scale is for cross-program workflows, advanced approvals, API writes, webhooks, and implementation support.
  • Network adds custom governance, entity boundaries, partner workspaces, and organization-wide rollout requirements.