ActionLoopsUpdated September 2026

How do I add a Loops contact?

Short answer: You can create loops contact in Loops by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Loops Create Loops Contact action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create Loops Contact in Loops — start free All 2 Loops actions

Create Loops Contact in Loops — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Email email	email	Required	The email address. Used as the recipient or identifier depending on context.
First Name firstName	string	Optional	Contact's first (given) name.
Last Name lastName	string	Optional	Contact's last (family) name.
Source source	string	Optional	Source. e.g. "website"

Sample request

{
  "email": "e.g. user@example.com",
  "firstName": "e.g. Jane",
  "lastName": "e.g. Doe",
  "source": "website"
}

Returns

{
  "id": "contact123",
  "success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Create Loops Contact.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Loops

2 Google Sheets triggers

HubSpot → Loops

18 HubSpot triggers

FAQ

Questions about Create Loops Contact.

What does the Create Loops Contact action do in Loops?

Adds a contact to Loops with email and custom properties. The base hook for "form submission → push to Loops for product-lifecycle email automation" workflows.

What inputs does Create Loops Contact require?

Required: Email. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Loops returns an error?

The run history shows the failed step with its input and the error message Loops returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Create Loops Contact support batch operations?

Run Create Loops Contact inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Loops's rate limits.

More actions

Other Loops actions.

Action

Send Loops Event

Pushes a semantic event ("user_completed_onboarding", "signup_completed") into Loops. Loops admin matches events to email automations and queues the right sends. The core workflow shape for behaviour-driven email.

Create Loops Contact in Loops — start free