ActionSendFoxUpdated September 2026

How do I add a SendFox contact?

Short answer: You can create sendfox contact in SendFox by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the SendFox Create SendFox 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 SendFox Contact in SendFox — start free All 1 SendFox actions

Create SendFox Contact in SendFox — 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 first_name	string	Optional	Contact's first (given) name.
Last Name last_name	string	Optional	Contact's last (family) name.
List IDs lists	string	Optional	Comma-separated list IDs

Sample request

{
  "email": "e.g. user@example.com",
  "first_name": "e.g. Jane",
  "last_name": "e.g. Doe",
  "lists": "{{trigger.lists}}"
}

Returns

{
  "id": 123,
  "email": "john@example.com",
  "created_at": "2026-04-11T10:00:00Z",
  "first_name": "John"
}

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

Triggered by

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

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

Google Sheets → SendFox

2 Google Sheets triggers

HubSpot → SendFox

18 HubSpot triggers

FAQ

Questions about Create SendFox Contact.

What does the Create SendFox Contact action do in SendFox?

Adds a subscriber to SendFox with email, name, optional notes. For "form submission → push to SendFox newsletter" cost-conscious creator workflows.

What inputs does Create SendFox 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 SendFox returns an error?

The run history shows the failed step with its input and the error message SendFox 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 SendFox Contact support batch operations?

Run Create SendFox 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 SendFox's rate limits.

Create SendFox Contact in SendFox — start free