Skip to main content

General

Everything you built in the Workflow Builder is now called a Workflow. Your existing Workflows are on the Agents page, in the same list as all other Agents. To see only Workflows, filter the list by Type > Workflow. Nothing changes in the way they run unless you migrate them to Agents.
While Agents are in public beta, running them doesn’t use credits. Credit billing for Agents starts after the beta.Workflows still use credits as before, including Workflows that an Agent runs as a step.Once billing starts, an Agent run uses more credits than the same task run as a Workflow, because the Agent reasons through each step and that reasoning uses credits. To keep your credit use down:
  • Keep high-volume, fixed tasks as Workflows. Run them on their own, or as a step inside an Agent so the Agent only reasons about the parts that need judgment.
  • Check how often triggers fire. Every triggered run is a full run. An hourly monitor, for example, can start up to 24 runs a day.
Learn more in Profound usage pricing: Credits.
No. Bulk runs with Sheets are currently supported only for Workflows. The Workflows you built in the Workflow Builder can still run in Sheets as normal.
No. All data in Agents is contractually prohibited from being used by third-party AI providers (such as OpenAI, Anthropic, or Perplexity) to train or improve their underlying models.
No. An Agent reasons through the task each time, so wording and steps can vary between runs. If you need certain things to stay the same (format, data sources, tone of voice), tell Aim in the Agent’s chat. If you need identical output and the same sequence of steps on every run, use a Workflow, either on its own or as a step inside an Agent.
No. Changes you make to an Agent apply right away, and every run uses the current version. There are no separate test runs: run the Agent with Run Agent, check the result in its chat, and ask Aim for changes if you need them.
Check the following in the Agent’s settings panel:
  • The trigger’s own switch is on. When it’s off, that trigger is paused. Only the person who created a trigger can switch it.
  • The trigger is listed under Triggers. A trigger described only in the instructions, such as “every Monday”, doesn’t fire.
  • For Slack triggers, check the channel picker. To see private channels, message @Profound in Slack and link your account.
  • The Agent has been created. An Agent that’s missing a name or instructions shows as a draft, and its triggers stay paused until it’s complete. Hover over a paused trigger to see why.
Each run is its own chat, and you grant tool permissions per chat, so Allow once or Allow for this task doesn’t carry over. To stop the prompts for a tool action, select Always allow on the approval card, or set the action to Allow in the tool’s Tools & permissions settings. To change this for the whole Agent, set When a tool needs approval under Advanced settings to Approve.
Not yet. Workflows work with both the Profound API and MCP. Agents currently work only in the Profound platform.
Only you, by default. Select Share to invite teammates with Can view or Can edit access, or set General access to everyone in your organization. Shared Agents appear under Shared with me for the people you share them with. Runs started by a trigger are visible to the person who set the trigger.
Yes. Open Version history from the … menu on the Agent’s page, review earlier versions, and select Restore to bring one back.
Turn off each trigger’s switch under Triggers in the Agent’s settings panel to pause it, and turn it back on to resume. To stop automatic runs permanently, remove the Agent’s triggers.
Yes. In the … menu, select Submit as template, pick a category, and choose who can use it: your organization or all Profound customers. Profound reviews every submission before it appears. Track your submissions under My template submissions.

Agents vs Workflows

Agents built with Aim work for most tasks, so we recommend using them. When you need the same steps on every run, or full control over the steps and their order, use a Workflow. You can also combine them: an Agent can run a Workflow as one of its steps. Learn more in Agents and Workflows: when to use which.
Yes. In the Agent’s instructions, type /, open Agents, and pick a published Workflow. During a run, the Agent starts the Workflow, fills in its inputs, and uses its results in the next steps. You can follow the Workflow’s run in the Agent’s chat and open it to see what each node returned. Learn more in Agents and Workflows: when to use which.
Only published Workflows that you have access to are listed. Publish the Workflow in the Workflow Builder, or ask its owner to share it with you.
Anyone who runs the Agent needs access to every Workflow it uses. Share the Workflow with them, too.
No. An Agent can run Workflows as steps, but not other Agents.
No. Your Workflows keep running as they are, so you don’t have to migrate any of them. To use a Workflow with an Agent’s triggers or reasoning, add it to an Agent’s instructions and the Agent runs it as a step.
Yes. When you migrate a Workflow, Aim writes instructions based on it and then reasons through them instead of following the nodes, so the results are close but not identical. Run the migrated Agent and adjust the instructions before you rely on it. Your original Workflow stays unchanged. See Migrate a Workflow to an Agent.
Migrate a Workflow if you need:
  • Easier updates: describe the change in the Agent’s chat, and Aim makes it.
  • Flexibility with unexpected inputs, or a fix for a Workflow that keeps breaking: the Agent reasons through the run and works around common issues.
  • Triggers beyond a schedule. Learn more in Triggers in Agents.
Profound is rebuilding the Workflow template library as Agent templates. To browse templates that aren’t rebuilt yet, open the Templates page and switch the type filter from Agents to Workflows.

Content creation

Both are possible, and you control which approach your Agents take. Agents can generate recommendations and surface them for human review before any content is published, or publish directly to your content management system (CMS) without a manual approval step. Most teams start with a review step and automate publishing once they’re confident in the output quality.
Yes. A common use case for Agents is to pull Profound visibility data or run a Google Search query, identify gaps or underperforming topics, and then generate content briefs or full articles. The Agent can then pause for a human review or publish the content directly to your CMS.
No. All content generation in Agents goes through secure, enterprise-tier API connections rather than public-facing consumer apps, such as the public ChatGPT or Gemini apps.

Tools and integrations

Yes. Agents can publish to WordPress, Webflow, Contentful, and Sanity through tools, and Workflows support more CMS platforms through integrations. To publish to a CMS that’s only available to Workflows, have your Agent run a Workflow that publishes there. Learn more in Integrations vs connectors: what’s the difference?.
Agents don’t support Shopify as a tool yet. In Workflows, you can push data to and pull data from Shopify with an API call, which brings product content, catalog data, or e-commerce signals into your answer engine optimization (AEO) work. To use that data in an Agent, add the Workflow to the Agent’s instructions. Native Shopify support is planned for a future release.
Agents support Google Analytics as a tool: add it to an Agent to pull Google Analytics 4 (GA4) data into a run. Looker Studio isn’t available as a tool. As a workaround, connect your Agent’s outputs to your Looker Studio reporting pipelines.
There’s no direct Reddit integration, but several Workflow templates cover Reddit analysis and engagement, such as the Reddit Insights Generator and Reddit Comment Generator. They identify top-cited Reddit threads, surface key discussion themes, and generate on-brand comments.

Workflows

The Prompt LLM node supports a variety of models, including the latest from Anthropic, OpenAI, and AWS Bedrock. Select any available model. Bringing your own API keys isn’t supported.