Skip to content
Recued
Menu
← Back to recipes

Create an Outreach snippet

by recued-core v1

Approval-gated Outreach snippet creation. It reads existing snippets for context, then creates one snippet through recued-core.outreach.snippet.create with an explicit name and HTML body. It does not update snippets, delete snippets, associate snippets with sequence steps, create sequence steps, send mail, or call arbitrary Outreach endpoints.

How it works 8 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (8 steps)
name trim
Trim whitespace from setting name
body_html trim
Trim whitespace from setting body html
existing_snippets ?
has_name compare
Check if name has data
has_body compare
Check if body html has data
ready all
Check if all conditions are true
create_snippet ?
skip: step.ready not_equal true
card to_summary
Format results as a summary card
Settings 3 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

name setting =
outreach setting =
body html setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Outreach connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.typedata.attributes

About

Tags

outreach outreachsnippetsales-contenttemplateapprovalpack:outreach

Details

8 steps 3 configurable settings recipe_id: create-outreach-snippet