Agent Builder is in beta. Some features are still in development and are subject to change.
This quickstart walks through building a new agent that summarizes meeting notes in different formats for various stakeholders.

Interface

Interface

Blueprint

Blueprint
You will:
If you are unfamiliar with Agent Builder:

​
Create a new Agent Builder project

To create an agent with Agent Builder, log in to AI Studio and follow these steps:
1

Click the Build an agent button

Click the Build an agent button in the top right corner of the page.Build an agent button
2

Create a new agent

In the modal that appears, select New Agent to create a new agent from scratch.
For common use cases, prebuilt agent templates are available. These include both general-purpose and industry-specific options, all customizable to your specific requirements.
Agent creation optionsOnce the agent is created, a new tab will open in your browser with the Agent Builder interface.
3

Return to the Agent Builder interface

You can get to the Agent Builder interface any time by going to the AI Studio homepage and selecting the agent you created.You’ll see the Configure Deployment page when you select the agent. To get to the edit interface, click the Edit button in the top right corner.Edit agent

​
Clear the demo agent

When you create a new Agent Builder project, a demo agent is automatically created for you. You can remove the demo agent’s components and blueprints to start building your own agent.

​
Clear the UI

1

Delete the top-level Page component from the Component Tree

Navigate to the Interface view. Then select the Interface Layers section in the left sidebar.Click the top Page component from the UI component tree.Select the top-level Page elementThen click the three vertical dots on the Page’s settings menu to find the Delete option.Delete page
2

Add a new Page

Your Component Tree should now contain a single Root component.Click Add page at the bottom of the component tree to create a new blank page.Add page

​
Clear the blueprint

1

Delete the first component under Blueprints Root

Navigate to the Blueprints view. Then select the Blueprints Layers section in the left sidebar.Click the first component under Blueprints Root. Here, the component is a blueprint called BUTTON@CLICK_1.Find the blueprint in the component treeThen click the three vertical dots on the blueprint’s settings menu to find the Delete option.Delete blueprint
2

Add a new Blueprint

Your blueprint’s component tree should now be empty.Click Add blueprint at the bottom of the component tree to create a new blank blueprint.Add blueprint

​
Build the UI

Now that you have an empty page, build the UI for the new agent. This agent has the following components:
  • A Textarea Input for users to paste their meeting notes
  • A Select input for users to select the summary format they want
  • A Button to start the summarization process
  • A Message component to display a loading message while summarization is in progress
  • A Text component to display the summary
Navigate to the Interface view to build the UI.

​
Add the Textarea input

The Textarea Input component is where users can paste their meeting notes.
1

Add the Textarea Input component to the canvas

Make sure you are in the Interface view. Then open the Add block section in the left sidebar and search for the Textarea Input component in the component library.Click and drag the Textarea Input component onto the canvas.
2

Edit the Textarea input component settings

Click the Textarea component you just added to edit its settings. Update the following settings:
  • Label: Meeting notes
  • Placeholder: Paste your meeting notes here.
  • Link variable under Binding: meeting_notes. This allows the blueprint to access the meeting notes content whenever the user updates it.
The “link variable” is stored in the agent’s state. The state is a set of variables that both the blueprint and the UI can access and update. You can learn more about the agent’s state in Agent state.
The component should now look like this:Textarea input settings

​
Add the select input

The Select input component is where users can choose what type of summary they want via a dropdown.
1

Add the select input component to the canvas

Search for the Select input component in the component library on the left side of the page.Click and drag the Select input component onto the canvas.
2

Edit the select input component settings

Click the Select input component you just added to edit its settings. Update the following settings:
  • Label: Summary format
  • Options: Add the options you want to display in the dropdown. For this example, add the following options, with the key and the value both set to the option name.
    • Executive brief
    • Action items only
    • Full summary
    • Key decisions
  • Link variable under Binding: summary_format. This allows the blueprint to access the selected format whenever the user changes it.
The component should now look like this:Dropdown input settings

​
Add the summarize button

Next, add a Button component to the UI that triggers the summarization process. You will connect this button to the blueprint in a later step.
1

Add the button component to the canvas

Search for the Button component in the block library on the left side of the page. Then click and drag the Button component onto the canvas.
2

Edit the button component settings

Click the Button component you just added to open its settings. Update the following settings:
  • Text: Generate summary
The component should now look like this:Button component settings

​
Add the progress message component

The Message component displays messages to users. Here, you use it to display a loading message while summarization is in progress.
1

Add the message component to the canvas

Search for the Message component in the block library. Then click and drag the Message component onto the canvas.
2

Edit the message component settings

Click the Message component you just added to edit its settings. Update the following settings:
  • Message: @{status}. This reads from the status state variable, which the blueprint will set to indicate the progress of the summarization.
The component should now look like this:Message component settings

​
Add the summary text component

The Text component is where the blueprint displays the meeting summary when it’s complete.
1

Add the text component to the canvas

Search for the Text component in the block library on the left side of the page. Then click and drag the Text component onto the canvas.
There are multiple components with the name Text in them. Make sure you select the Text component under the Content section of the component library.
2

Edit the text component settings

Click the Text component you just added to edit its settings. Update the following settings:
  • Text: @{summary}. This displays the value of the summary state variable, which the blueprint sets to the meeting summary.
  • Use Markdown: Select Yes. This allows you to use markdown formatting in the text.
The component should now look like this:Text component settings

​
Build the blueprint

With the UI built, you can now build the blueprint for the new agent. The blueprint has the following logic:
  1. The UI trigger block triggers the blueprint when the user clicks the Generate summary button in the UI.
  2. The Set state block sets the status state variable to Summarizing so that the Message component in the UI can display it.
  3. The Text generation block generates a summary of the meeting notes based on the selected format.
  4. The Set state block sets the summary state variable to the generated summary so that the Text component in the UI can display it.
  5. The Set state block sets the status state variable back to an empty string to clear the loading message from the UI.
Navigate to the Blueprints view to build the blueprint.

​
Add the UI trigger

The UI trigger block triggers the blueprint when the user clicks the Generate summary button in the UI.
1

Add the UI trigger block to the canvas

Make sure you are in the Blueprints view. Then open the Add block section in the left sidebar and search for the UI trigger block in the blueprints toolkit.Click and drag the UI trigger block onto the canvas.
2

Edit the UI trigger block settings

Click the UI trigger block you just added to edit its settings. Update the following settings:
  • Component ID: Select the button component (it should show as Generate summary)
  • Event type: wf-click. This triggers the blueprint when the user clicks the Generate summary button in the UI.
The block should now look like this: UI trigger settings

​
Add the set state block for the progress message

The Set state block sets the status state variable to Summarizing so that the Message component in the UI can display it.
1

Add the set state block to the canvas

Search for the Set state block. Then click and drag the Set state block onto the canvas.Connect the Set state block to the UI trigger block by dragging a line from the green dot on the UI trigger block to the Set state block. This tells the blueprint to execute the Set state block after the UI Trigger completes.
2

Edit the set state block settings

Click the Set state block you just added to edit its settings. Update the following settings:
  • Link variable: status
  • Value: % Generating summary. The % symbol indicates that the message should display a dynamic loading symbol.
The Message component in the UI displays the loading message when this block is executed.The block should now look like this:Set state block settings for the status message
At this point, you can preview the agent to see the new behavior. When you click the Generate summary button, the Message component displays the loading message that you set in the Set state block. Preview the agent

​
Add the text generation block

The Text generation block generates a summary of the meeting notes based on the selected format using Palmyra LLMs.
1

Add the text generation block to the canvas

Search for the Text generation block in the block library. Then click and drag the Text generation block onto the canvas.Connect the previous Set state block to this Text generation block. Drag a line from the green dot on the Set state block to the Text generation block. This tells the blueprint to execute the Text generation block after the Set state block completes successfully.
2

Edit the text generation block settings

Click the Text generation block you just added to edit its settings. Update the following settings:
  • Prompt: Enter the following prompt. This prompt references the meeting_notes and summary_format state variables, which you set up in the UI. It instructs the agent to summarize the meeting notes and defines the different formats.
Summarize these meeting notes based on the requested format:

Meeting Notes: @{meeting_notes}
Format: @{summary_format}

Guidelines for each format:
- Executive brief: Create a concise 2-3 sentence overview focusing on high-level outcomes and decisions for leadership
- Action items only: List only the specific action items, who is responsible, and deadlines
- Full summary: Provide a comprehensive summary including discussion points, decisions, action items, and next steps
- Key decisions: Focus specifically on decisions made during the meeting and their implications

Format the output appropriately for the selected format type.
The block should now look like this:Text generation block settings

​
Add the set state block for the summary result

This Set state block sets the summary state variable to the generated summary so that the Text component in the UI can display it.
1

Add the set state block to the canvas

Search for the Set state block in the block library. Then click and drag the Set state block onto the canvas.Connect the new Set state block to the Text generation block. Drag a line from the green dot on the Text generation block to the new Set state block. This tells the blueprint to execute the new block after the Text generation block completes successfully.
2

Edit the set state block settings

Click the Set state block you just added to edit its settings. Update the following settings:
  • Link variable: summary
  • Value: @{result}. The result environment variable is the output of the previous Text generation block.
The @{result} syntax is how you reference the output of previous blocks. Learn more about what data and variables are available to reference in Using data from previous blocks.
The block should now look like this: Set state block settings for the summary result

​
Add the set state block to clear the status message

This Set state block clears the status state variable to remove the status message from the UI.
1

Add the set state block to the canvas

Search for the Set state block in the block library. Then click and drag the Set state block onto the canvas.Connect the new Set state block to the previous Set state block. Drag a line from the green dot on the previous Set state block to the new Set state block. This tells the blueprint to execute the new block after the previous block completes successfully.
2

Edit the set state block settings

Click the Set state block you just added to edit its settings. Update the following settings:
  • Link variable: status
  • Value: Leave the Value blank. This clears the status state variable.
The block should now look like this: Set state block settings to clear the status message

​
Data connection patterns

Notice how the blueprint connects blocks and passes data using variables:
  • @{meeting_notes} and @{summary_format}: the blueprint blocks read from UI inputs via state
  • @{result}: the blueprint blocks read the output from the Text generation block
  • @{summary}: the blueprint blocks write the summary to the state, which the UI displays
  • @{status}: the blueprint blocks set progress messages that the UI displays
This pattern of using @{variable_name} is how all Agent Builder components communicate.

​
Preview the agent

You’ve now built the UI and blueprint for the new agent. Go to the Preview view to test the agent. Paste meeting notes into the Meeting notes text area and select a summary format from the Summary format select input. Then click the Generate summary button to see the agent create a summary in your selected format. Here is a sample transcript that you can use to test if you don’t have your own meeting notes: Try different summary formats with the same meeting notes to see how the output changes based on your selection. You can also experiment with leaving the summary format blank to see how the agent handles it. If you encounter any issues, refer to the Troubleshooting guide for debugging information.

​
Deploy the agent

When you’re ready to deploy the agent, click Configure deployment in the top right corner of the Agent Builder interface. You can also access the deployment configuration by going to the AI Studio homepage and selecting the agent you created. If the agent isn’t deployed, you see a toggle bar that says Draft. Agent that is not deployed To deploy the agent, toggle the bar. Writer deploys the agent to the Writer cloud, which takes a moment to complete. When the agent is deployed, the toggle bar shows Deployed. It also shows a list of the teams in your organization, which you can use to grant access to the agent. You must select at least one team before you can view the URL for the deployed agent. Agent that is deployed You can also choose to deploy the agent to the Writer Agent Library for the teams you’ve granted access to. These teams can see the agent you’ve created in the main Ask Writer app. To help teams find the agent, select Edit the agent guide, where you can add a description and other information to help teams use the agent. Edit the agent guide

​
Agentic enhancements

This tutorial shows outcome-driven design in action: you define what kind of summary you want, and the agent adapts. To make this agent even more powerful, consider adding:
  • Send summaries to Slack: Automatically post to relevant channels
  • HTTP request blocks and tool calling to integrate with third party APIs to perform actions like:
    • Emailing participants: Send summaries via your email API (SendGrid, Mailgun)
    • Calendar integrations: Schedule follow-up meetings and block time for tasks
    • CRM updates: Log meeting outcomes in your customer database
    • Task automation: Create Jira tickets or Asana tasks for each action item
These integrations transform a summarizer into a true meeting assistant that takes action on your behalf.

​
Next steps

Bug report

Report a bug in Agent Builder.

Feature request

Request a new feature in Agent Builder.