Utopian Labs icon

Utopian Labs

Use Utopian Labs AI to research and engage with leads

Actions6

Overview

This node integrates with Utopian Labs AI to perform various lead-related operations, including researching leads, qualifying them, classifying, writing emails, and specifically for the "Trigger a Timing Run" operation, it initiates a timing-based agent run. This operation is useful when you want to start an AI-driven timed research or engagement process on a lead's company website, with callbacks to continue workflow execution upon completion.

Typical use cases include:

  • Automatically triggering AI agents to analyze or engage with a lead based on their company website.
  • Running timed research steps that can be awaited asynchronously in workflows using a Wait node configured to listen for webhook callbacks.
  • Testing workflows by optionally returning mock responses without running actual agents.

Example: You provide the lead’s company website and select the Timing Agent; the node triggers the agent to start processing and sends results back via a callback URL, allowing your workflow to proceed once the agent finishes.

Properties

Name Meaning
Lead Company Website The website URL of the lead's company. Must be a valid URL format.
To use the result of this agent run, add a Wait node and set it to "On Webhook Call". Important: Make sure the Wait Node is set to POST.
The webhook URL will automatically be set by the default parameter.		 Informational notice guiding how to handle asynchronous callback results from the agent run.
Callback Url The URL where the agent should send its callback after completing the run. Typically, this is the URL of a Wait node configured to receive the webhook call. Defaults to the workflow’s resume URL.
Return Mock Response Boolean flag indicating whether to return a mock response instead of running the actual agent. Useful for testing workflows without invoking real AI runs.
Agent Select which timing agent to use for the run. Options are:
- Timing Agent
- Timing Agent Light
Additional Fields A collection of optional fields to provide more context about the lead:
- Lead Company Name
- Lead Company Description
- Lead Full Name (required if other lead info provided)
- Lead Business Email Address (must be valid and not from blocked domains)
- Lead LinkedIn Profile URL
- Lead Job Title
- Lead X/Twitter Handle
- Max Research Steps (number, default 5)
- Context (additional text context)
- Use Memory (boolean, whether to use previous research data)

Output

The node outputs JSON data representing the result of the triggered timing agent run. The structure depends on the agent’s response but generally includes details about the lead research or engagement performed.

  • The output JSON array contains one item per input item processed.
  • Each item includes the agent’s response data.
  • If Return Mock Response is enabled, the output contains simulated data for testing purposes.
  • No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with Utopian Labs AI services.
  • The node makes HTTP POST requests to the Utopian Labs API endpoint /v1/n8n/runs.
  • The workflow must include a Wait node configured to receive webhook callbacks (POST method) at the specified callback URL to handle asynchronous results properly.

Troubleshooting

  • Invalid email address error: Occurs if the provided lead business email is not in a valid format or uses a blocked domain. Ensure the email is correctly formatted and not from generic domains like gmail or hotmail.
  • Invalid website URL error: Triggered if the lead company website URL does not match expected URL patterns. Verify the URL is correct and includes protocol (http/https).
  • Lead full name required: If any lead-specific information (email, LinkedIn, job title, Twitter handle) is provided, the lead full name must also be supplied.
  • Callback handling: If the Wait node is not configured correctly (e.g., not set to POST or missing), the workflow may not resume as expected after the agent run completes.
  • API errors: Network issues or invalid API credentials will cause request failures. Check API key validity and network connectivity.

Links and References

Discussion