Custom Workflows
When the templates don't fit, build it yourself.
Last updated:
If nothing in the marketplace fits your exact needs, you can build a custom workflow in Workflows. If there’s a marketplace workflow that’s almost there, you can also fork it so you don’t have to start from scratch.
But, before you place a single node, answer these three questions clearly:
What are you trying to accomplish?
You probably already have a pretty good idea what needs doing, or you would stick with marketplace workflows. But it’s important to have absolute clarity here or you could end up spending a bunch of time creating a monstrosity of a workflow that’s trying to do too much, at the expense of time wasted currently doing nothing.
Create a list of the steps you’d need before ever touching nodes to accomplish your goal.
For example if you are trying to “find users where they are”:
- Watch Reddit for keywords
- Read the content that matches the keywords
- Have AI draft 3 content-aware responses that provide value and mention your product in passing.
- Ping you on Slack with the URL to the post, the matched keyword(s), and the three drafts.
What parts of the problem should you automate?
Taking a look at the example list above, you could have chosen to post to Reddit automatically (though, we don’t support that in order to make sure you’re not using SessionSight as a spamming tool).
That’s a bad use of automation. Your goal should be to cut down the time it takes you to do your marketing, not to automate away every chance you have at learning more about how users see your product, your brand, and excluding you from conversations that otherwise would have helped you gain insight you might never have gotten alone.
This is especially important when generating AI content for platforms where spam is explicitly prohibited (like Reddit), because most people can immediately tell when something is AI slop, and that defeats the entire purpose of your marketing efforts.
Other things, like pinging you about bad session quality, can be fully automated because you’re the human on the other end of the output, and you get to decide how much noise you want.
Is this driving meaningful output?
SessionSight’s workflows are incredibly powerful, which also means that you can spend a lot of time doing cool builds that don’t move the needle for you. Remember that the point of running these campaigns is to drive traffic, gain better insights, alert you to problems, or similar tasks that are business critical.
Some basics
What are triggers?
To put it simply, these are the starting point for work.
Some options available to you:
- One-time trigger: Fires once per-campaign start.
- Keyword monitors: Fires every time a keyword matches a post/comment on a platform.
- On Feedback: Fires when a user submits feedback.
- Session Quality: Fires when a live session drops below a quality/experience threshold.
- Goal based: Fires when you complete or change the value of a goal.
There are a variety of other triggers you can see in the workflow editor’s sidebar under Triggers. Workflows don’t have to have one trigger either, they can have multiple, running in parallel.
The types of handles
Some nodes have handles on the top of the node. Those are “flow” handles that dictate the progression of the workflow. They can only ever be attached to one other node.
The other handles you’ll see on nodes, which are always in the body of the node, are input or output handles. They allow you to chain values to and from nodes so that you can create compounding values, or use the output from nodes like AI generation.
Workflows are versioned
When you want to add a workflow to a campaign, you will have to “publish” a version. This doesn’t publish it to the marketplace, just locks that version so that you can keep making changes to the workflow without impacting your running campaigns that use it.