Suger

Getting Started with Workflows

Automate repetitive marketplace tasks by building workflows that react to events, apply your rules, and take action across your connected tools.

Overview

Every workflow follows the same three-part logic. Understanding this structure before you build makes it easier to plan what each workflow needs to do:

  1. Trigger: An event that starts the workflow, such as a referral approval, a new private offer, or a completed transaction.
  2. Conditions: Rules that control when the workflow runs. For example, only fire if the cloud partner is AWS and the deal value is above $50,000.
  3. Actions: What happens when the trigger and conditions are met, such as sending a Slack message, updating a CRM field, or uploading a report to Google Drive.

You have two ways to get started: begin from a pre-built template, or build a custom workflow from scratch in the visual builder.

Option 1: Start from a template

If your use case is common, templates are the fastest way to get a workflow running. Templates come pre-configured with the core logic already in place, so you only need to adjust a few settings before activating.

Access the template library

  1. Go to Workflows in the Suger Console.
  2. Click the Templates tab to browse available automations by category (Reporting, Notifications, CRM Sync).

Available templates

  • Private offer notifications: Sends branded email alerts to customers when a private offer is pending, including offer terms and contact details.
  • Weekly entitlement report: Runs on a schedule to compile active and canceled entitlements into a CSV file and upload it to Google Drive or Snowflake.
  • API-driven updates: Uses a webhook trigger to connect Suger to your internal systems, so your API can automatically update offer contacts or EULA terms.

Activate a template

  1. Select a template to open it in the visual builder. The core logic is already filled in.
  2. Verify the destination settings, such as your Slack channel name or email domain.
  3. Choose how the workflow fires: by a real-time event (Webhook), on a schedule (Cron), or manually.
  4. Toggle the workflow to Active.

Option 2: Build a custom workflow

For automations that go beyond what templates offer, you can build your own workflow from scratch in the visual builder.

Plan your workflow first

Before opening the builder, take a few minutes to define the following. This prevents common issues like missing data fields or unclear logic once you start connecting nodes.

  • What problem does this solve? State the manual or repetitive task you are automating. For example: “AEs have to manually check for referral approvals and notify the team.”
  • What does success look like? Define the expected outcome. For example: “AEs receive a Slack message with AWS contact details within 5 minutes of a referral being approved.”
  • Where does the trigger come from? Identify the origin system, such as the Suger Console, Salesforce, or the AWS Partner Central API.
  • What data is needed? List every field required to complete the action, such as Opportunity Owner, AWS Account Manager, Customer Name, and Deal Context. Missing fields will cause the workflow to fail silently.
  • When should it not run? Define any exceptions, such as “skip if no Account Manager is assigned” or “only run for deals above $50,000.”

Build the workflow

  1. Go to Analytics > New Dashboard and select the Workflows tab, or navigate directly to Workflows in the Suger Console.
  2. Click New Workflow to open the visual builder canvas.
  3. Drag a Trigger node onto the canvas and configure the event that starts the workflow.
  4. Add Condition nodes to define the rules that control when the workflow proceeds.
  5. Add Action nodes to define what happens at the end of the workflow, such as sending a notification or updating a record.
  6. Connect nodes to external platforms as needed. Supported integrations include Salesforce, HubSpot, NetSuite, Snowflake, and Google Drive.

Test before publishing

  1. Use the built-in test tool to simulate an event through the workflow.
  2. Confirm that each node processes correctly and that conditional branches behave as expected.
  3. Check that data outputs from the trigger (such as an Opportunity ID) are correctly mapped to the inputs of your action nodes.

Publish the workflow

Once testing passes, click Publish to activate the workflow.

Monitor workflow runs

After a workflow is live, use Execution History in the Suger Console to track every run in real time. If a workflow fails, the logs show which node encountered the issue and what data was present at that point, making it easier to identify and fix the problem.