The Connector Library and Connections

StretchAutomate distinguishes between a connector and a connection:

A connector is a capability — a StretchSuite app (or Webhook/HTTP, or Built‑in logic) that offers triggers (events that start a workflow) and actions (things a workflow can do). Connectors are built in; you browse them in the Library tab.
A connection is a linked account — a named, credential‑bearing reference that lets a workflow actually reach a connector. You manage connections in the Connections tab.

You need the connector to know what is possible and the connection to do it for real.

The connector library

Every connector in the Library lists exactly which triggers and actions it supports:

Connector	Triggers	Actions
StretchCRM	`lead_created`, `deal_stage_changed`, `contact_created`	`create_contact`, `update_deal`, `add_tag`
StretchMail	`email_received`	`send_email`, `add_to_list`
StretchForms	`form_submitted`	—
StretchShop	`order_created`, `cart_abandoned`, `checkout_completed`	`create_order_note`, `tag_customer`
StretchBooks	`invoice_paid`	`create_invoice`, `record_payment`
StretchTasks	`task_completed`	`create_task`
StretchSchedule	`appointment_booked`, `appointment_canceled`	`create_event`
StretchSocial	—	`schedule_post`
StretchSupport	`ticket_created`, `sla_breach_imminent`	`create_ticket`, `reply`
Webhook / HTTP	`inbound_webhook`	`http_request`
Built‑in logic	`schedule`	`filter`, `delay`, `transform`

A few things to notice: StretchForms is trigger‑only (great for starting automations), StretchSocial is action‑only (you schedule posts but don't trigger from it), and Built‑in logic provides the filter, delay, and transform steps plus the schedule trigger — no connection required.

Creating a connection

Connections let a workflow authenticate to a connector. Crucially, a connection stores a credential reference (auth_ref) — a pointer to a securely held secret — never the plaintext secret itself.

Open the Connections tab and choose New connection.
Select the connector it is for (e.g. StretchMail) — required.
Give it a clear name (e.g. Marketing mailbox) — required. A descriptive name matters when several connections exist for the same connector.
Provide the credential reference and any metadata the connector needs.
Save. New connections default to active and are immediately usable by workflows.

Internal StretchSuite connectors typically need little or no setup because they are native to your platform; the Webhook/HTTP connector is where external credentials most often apply.

Managing connections

A connection carries a status (active by default). A connection that is not active cannot dispatch its connector's actions.
You can keep multiple connections per connector — for example separate mailboxes or environments — and choose which one a workflow uses.
Connections are scoped to your organization on the workspace surface: you only see and manage your own.

Realistic example

A team automates order follow‑ups. In the Library they confirm StretchShop offers the order_created trigger and tag_customer action, and StretchMail offers send_email. In Connections they create Store mailbox for StretchMail (active). Their workflow's email step uses that connection to send; the tag step uses the built‑in StretchShop capability. Later they add a second StretchMail connection, Support mailbox, and point a different workflow at it — same connector, two connections, cleanly separated.

Tips

Browse the Library first when designing — it tells you which triggers and actions actually exist, so you don't design around a capability a connector doesn't offer.
Name connections for their purpose, not just their connector, so you can tell Marketing mailbox from Support mailbox at a glance.
Remember connections hold a reference, never a raw secret — rotating the underlying credential doesn't require rebuilding the connection.
If an action step fails across many runs, verify its connector has an active connection before touching the workflow logic.

Troubleshooting

"connector and name are required." Creating a connection needs both a connector and a name. Provide both.

An action never seems to take effect. Confirm the connector has an active connection, and that you're running in live mode (simulate never performs real side effects).

I can't find a trigger I expected. Not every connector offers every event — check the Library table above. For example, StretchSocial has no triggers and StretchForms has no actions.