Create a Quo contact intake
Approval-gated Quo contact intake workflow. It reads contact custom field definitions for context, then creates one contact through recued-core.quo.contact.create with documented defaultFields and source metadata. It does not delete contacts, mutate phone settings, send messages, create tasks, create webhooks, or call arbitrary Quo endpoints.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (10 steps)
trimmed_first_name
trim
Trim whitespace from setting first name
trimmed_phone
trim
Trim whitespace from setting phone
trimmed_email
trim
Trim whitespace from setting email
has_first_name
compare
Check if trimmed first name has data
has_phone
compare
Check if trimmed phone has data
has_email
compare
Check if trimmed email has data
ready
all
Check if all conditions are true
custom_fields
?
create_contact
?
skip: step.ready not_equal true
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
quo
setting
=
role
setting
=
email
setting
=
phone
setting
=
source
setting
=
recued
company
setting
=
last name
setting
=
first name
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.