Changelog

Overview:

We’ve launched the OpenRouter app for HighLevel Workflows, enabling user to use AI model responses directly into their automations. With OpenRouter, users can now use multiple models like Perplexity, Claude, OpenAI, Gemini and many more. Upto 300+ of them.

What’s Improved?

HighLevel workflows can now invoke AI models via OpenRouter to generate real-time responses from custom prompts. Teams can automate content creation, summarization, and personalized messaging using system-level instructions and workflow variables.

Key Enhancements

Actions (HighLevel → OpenRouter)

Use AI-generated outputs directly within your workflows:

Generate Response

– Send a prompt to a selected OpenRouter AI model and receive a generated response that can be reused across workflow steps.

Action Capabilities

System Prompt (Optional) – Define the AI’s role, tone, or behavior (e.g., support agent, marketer, concise responder).

Prompt (Required) – Provide the main instruction, question, or task, including dynamic workflow variables.

Model Selection (Required) – Choose from multiple AI models based on quality, speed, creativity, and cost.

Why It Matters

Usecases like Manual content creation can now be plugged into a workflow. With OpenRouter in Workflows, users can:

Generate personalized emails, SMS, and WhatsApp messages at scale

Create any image or video content with models like veo.

Test Action

We have launched openrouter action with test action feature which will allow users to test the action before execution, allowing users to save the schema and use in subsequent actions as custom values.

Impact & Use Cases

1. AI-Powered Customer Replies

Automatically generate contextual email or SMS responses using contact data and inbound messages.

2. Message & Form Summarization

Summarize long form submissions or inbound conversations into concise notes or CRM fields.

3. Personalized Follow-Ups

Create tailored follow-up messages using workflow variables like name, service, or appointment details.

How to Connect

1. In Workflows, add an action and search for OpenRouter.

2. If not connected, click Connect Now and authenticate using your OpenRouter API key.

3. Select an AI model, configure your System Prompt and Prompt, then test the action.

4. Use the generated response in messages, custom fields, conditions, or downstream actions.

Best Practices

• Be specific in your Prompt for higher-quality responses

• Use the System Prompt to control tone and intent

• Test multiple models to find the best fit

• Keep prompts concise and clear

• Use workflow variables to personalize outputs

Frequently Asked Questions

Can I use workflow variables in the prompt?

Yes. You can use supported workflow variables in both the Prompt and System Prompt fields to generate personalized AI responses.

What is the difference between System Prompt and Prompt?

The System Prompt defines the AI’s role, tone, or behavior, while the Prompt contains the main instruction or question sent to the model.

Which AI model should I choose?

Model choice depends on your use case - lighter models work well for simple tasks, while advanced models are better for creative or complex responses.

Can I store the AI-generated response in a custom field?

Yes. The generated response can be mapped to custom fields, used in messages, or passed to other workflow actions.

Do OpenRouter actions cost extra in HighLevel?

Yes. OpenRouter actions and triggers are premium workflow actions and are billed at standard automation rates, in addition to OpenRouter usage charges.

Does HighLevel include AI credits for OpenRouter?

No. HighLevel does not include AI credits for OpenRouter. AI usage is billed by OpenRouter, along with standard automation rates in HighLevel. This will just like any other premium action.

Overview:

We’ve added native Monday.com actions and triggers to HighLevel Workflows, enabling real-time automation between HighLevel and Monday boards. This integration removes the need for third-party tools like Zapier or Make and allows teams to seamlessly sync boards, items, statuses, and updates directly within HighLevel.

What’s Improved?

HighLevel Workflows now support workflow actions and triggers with Monday.com, allowing agencies and teams to automate project management, onboarding, and internal operations without manual coordination or external automation platforms.

Key Enhancements

Triggers (Monday.com → HighLevel) (Coming soon)

These triggers fire near real-time when activity occurs in Monday.com:

Any Column Value Changed in Board – Fires when a specific column (status, date, owner, etc.) is updated.

Any Item Moved to a Group – Fires when an item moves between groups on a board.

New Board – Fires when a new board is created.

New Item in a Board – Fires when a new item is added to a board.

New Subitem in Board – Fires when a subitem is created under an item.

New Update in Board – Fires when a comment or update is added to an item.

New User – Fires when a new user joins the Monday.com workspace.

Actions (HighLevel → Monday.com)

Automate and manage Monday.com directly from HighLevel workflows:

Create New Board / Group / Column / Item / Subitem – Dynamically build Monday structures from workflows.

Update Item / Update Subitem – Update statuses, owners, dates, and custom columns.

Archive Board / Archive Group – Automatically archive completed boards or groups.

Delete Item / Delete Group – Remove items or groups when no longer needed.

Get Board Items – Retrieve all items from a board for syncing or reporting.

Find Items by Column Value – Search items using status, owner, or custom columns.

Find Items by ID – Locate a specific item using its Monday item ID.

Test Action

We have launched monday.com actions with test action feature which will allow users to test the action before execution, allowing users to save the schema and use in subsequent actions as custom values.

Why It Matters

Teams often manage projects in Monday.com while running CRM, communication, and automation flows in HighLevel. With native Monday.com actions and triggers, users can:

Keep HighLevel and Monday perfectly synchronized

Eliminate reliance on Zapier, Make, or custom webhooks

Use Cases

1. Client Onboarding Automation

Automatically sync new onboarding items from Monday.com into HighLevel CRM, notify account managers, and update item statuses once CRM actions are completed.

2. Project Status → Client Communication

Trigger emails, Slack notifications, or notes when a Monday item’s status changes (e.g., when a project is marked “Completed”).

3. Internal Task Sync Across Tools

When a task is created in Monday.com, automatically create corresponding tasks in ClickUp or other tools while maintaining cross-system references and visibility.

How to Connect

1. In Workflows, search for Monday.com triggers or actions.

2. If your account is already connected, configuration fields will appear automatically.

3. If not, click Connect Now and authenticate via Monday.com API key.

4. You can also connect anytime via:

Settings → Integrations → Monday.com

Google’s latest OAuth flow lets users select only some permissions (scopes) when connecting an app. That flexibility can leave required permissions ungranted, which then breaks features (e.g., connecting Google Business Profile).

This release adds clear in-app warnings and a one-click fix so users can grant missing permissions, if required.

What’s New

• Google Oauth from integration page now gives scopes with checkbox, Users can select scopes that they want.

  (It is recommended to select all scopes)

• Warning badge on the Google integration card whenever required scopes are missing.

• Details screen listing highlighting which scopes are missing, and which features are affected

• Reconnect CTA that re-runs Google OAuth so users can grant the additional scopes.

How to use:

1. Go to Settings → Integrations → Google.

2. If you see a warning on your primary Google account, click the message.

3. Review the missing scopes & affected features, then click Reconnect.

4. In Google’s consent screen, allow the additional scopes and finish.

5. Return to the integration page; the warning should be cleared.

Why it Matters

1. Reduces “it’s connected but not working” confusion.

2. Self-serve remediation for common tickets (e.g., “Primary Google connected, GBP is not connecting”).

3. Fewer support escalations.

Preview:

Permissions with checkbox in Oauth flow:

Warning on Google card, if all scopes are not added:

Permission feature mapping to guide which permissions affect which features