DESIGNER GUIDE
Use models, tools and connected capabilities
Select configured AI models, add controlled tools to workers and flows and connect the resources a solution needs without exposing unnecessary capabilities.
Scope: Agentic Worker, Flow project and deployment environment
Administrators configure. Designers select.
How a capability reaches a solution
Anything a designer can select was made available further upstream.
Tenant administration
↓
Configured providers and capabilities
↓
Workspace availability
↓
Worker or Flow selection
↓
Deployment environmentIntegration concepts
- Credential
- A configured connection that allows a supported model or provider to be selected.
- Provider
- The external or local service supplying the model or capability.
- Model
- The exact AI model used by a worker or bounded language step.
- Extension tool
- A packaged capability installed and exposed to the workspace.
- Flow as tool
- A reusable Greentic flow made available to an Agentic Worker.
- Built-in step
- A process capability supplied directly by Designer.
- Extension step
- A process step supplied by an installed extension.
- MCP capability
- A tool exposed through an approved Model Context Protocol connection.
- Deployment resource
- A worker, provider, capability or channel added to an environment.
Responsibilities
Configuration sits with administration. Selection and design sit with the solution designer.
| Task | Partnership or workspace administrator | Solution designer |
|---|---|---|
| Add provider credentials | Yes | No |
| Control tenant access and roles | Yes | No |
| Install or configure extensions | Yes | No |
| Connect MCP servers | Yes | No |
| Register component tools | Yes | No |
| Select an available model | No | Yes |
| Add an available extension to a worker | No | Yes |
| Add a reusable flow as a tool | No | Yes |
| Add supported steps to a Flow | No | Yes |
| Select a published Agentic Worker in a Flow | No | Yes |
| Add resources to a deployment environment | According to workspace permissions | According to workspace permissions |
Related guides: Admin AI and tools, Admin Guardrails, Agentic workers, Flows and Publishing and deployment.
On this page
Before you begin
Decide the minimum capability set before opening a worker or flow.
- Confirm that the correct workspace is active.
- Define what the solution needs to accomplish.
- Identify the minimum model and tool set required.
- Confirm that shared resources are available to the workspace.
- Verify that referenced workers or flows have been published where required.
- Define the input and output contract for every tool call.
- Prepare safe fictional test values.
- Know the approved fallback when a connected capability is unavailable.
1. Select a configured model
The Model tab connects a worker to a credential, a provider and one exact model.
- Credential
- The configured connection available to the workspace.
- Provider
- The service associated with the selected credential.
- Model
- The exact model identifier used by the worker.
- Temperature
- Controls how precise or varied responses may be.
- Maximum reply length
- Limits the size of the worker’s output where a concise answer is required.
- 1Open the worker’s Model tab.
- 2Select an available credential.
- 3Confirm the provider.
- 4Select the intended model.
- 5Set response variability appropriate to the use case.
- 6Set a maximum reply length where useful.
- 7Save the worker.
- 8Test representative requests.
- 9Repeat tests to confirm sufficient stability.
2. Add extension tools
Extensions give a worker the ability to act, within the boundary you define.
- Add extension
- Opens the list of available extensions.
- Search
- Finds an extension by name.
- Category filtering
- Narrows the list to one kind of capability.
- Extension name and description
- Explains what the capability does before you add it.
- Add
- Makes the capability available to the worker.
- 1Open the worker’s Tools tab.
- 2Select Add extension.
- 3Search for the required capability.
- 4Review its description.
- 5Confirm that the capability matches the worker’s responsibility.
- 6Select Add.
- 7Update the Behaviour instructions to explain when it may be used.
- 8Test the intended action.
- 9Test unavailable, failed and unsupported cases.
3. Add another Flow as a tool
Business actions belong in a deterministic Flow, not in the worker’s judgement.
- Add flow as tool makes an approved reusable Flow available to the worker.
- Use this when the worker needs to invoke a controlled business capability.
- The Flow should own deterministic validations, approvals and outcomes.
- The worker should know when it is allowed to call the Flow.
- The worker and Flow must agree on a stable input and output contract.
Agentic Worker
↓
Chooses an approved Flow tool
↓
Passes structured input
↓
Deterministic Flow executes
↓
Returns controlled resultThe Flow must be available to the current workspace and exposed through the controls provided by Designer.
4. Use built-in and extension steps
Flows reach connected capabilities through steps rather than through worker judgement.
- Steps
- Built-in capabilities supplied by Designer.
- Extension steps
- Additional step types supplied by installed extensions.
| Step | Integration role |
|---|---|
| Agentic Worker | Invoke a published worker |
| Go to Flow | Reuse another deterministic process |
| HTTP Call | Call an approved web endpoint |
| LLM Chat | Use a configured model for a bounded language task |
| MCP | Invoke an approved MCP capability |
| Human Approval | Connect a process to the runtime approval system |
| Card Render | Present or collect structured user data |
| Conditional Branch | Route using explicit values returned by another step |
5. Select an Agentic Worker inside a Flow
The Agentic Worker step is the controlled boundary between deterministic process and interpretation.
- Step name
- Give the process step a business-focused name.
- Agent
- Select the Agentic Worker the Flow should invoke.
- Conversational
- Off: receive one reply and continue the deterministic Flow. On: continue the worker conversation until it ends, then continue the Flow.
- 1Add an Agentic Worker step.
- 2Select the step.
- 3Enter a meaningful step name.
- 4Select the required worker.
- 5Decide whether the interaction should be one response or conversational.
- 6Pass only the required input.
- 7Connect the output to a controlled next step.
- 8Test the worker directly.
- 9Test it again through the Flow.
6. Add resources to a deployment environment
An environment is where channels, workers, providers and capabilities are connected.
- Channel
- The place through which users or systems reach the solution.
- Worker
- The worker that responds through the channel.
- Provider
- A configured provider resource required by the environment.
- Agentic Worker
- An available worker added to the environment design.
- Capability
- An approved supporting capability.
- Wiring assistant
- A control intended to help connect environment resources.
- Deploy environment
- Starts the deployment process after the environment has been configured.
Channel
↓
Worker
↓
Model provider
↓
Approved tools and capabilities
↓
Deployed environment- 1Open Deploy.
- 2Open the intended environment.
- 3Add the required channel.
- 4Add the worker.
- 5Add the required provider.
- 6Add only the capabilities the solution needs.
- 7Connect the resources using the current environment controls.
- 8Review the wiring.
- 9Use the Wiring assistant where appropriate.
- 10Deploy first to a safe non-production environment.
- 11Run a controlled post-deployment test.
7. Apply least privilege
Give each solution the smallest capability set that still delivers the outcome.
| Resource | Restrict |
|---|---|
| Model | Select only the model needed for the worker |
| Extension | Add only the capabilities required by the use case |
| Flow as tool | Expose only approved deterministic processes |
| HTTP or MCP | Use only approved endpoints and operations |
| Knowledge | Attach only relevant knowledge bases |
| Memory | Enable only when conversational continuity is required |
| Guardrail | Confirm that required protections are installed and operational |
| Deployment environment | Add only the channels, workers and capabilities required for that environment |
8. Test connected capabilities
Test the failure paths as deliberately as the successful ones.
| Scenario | Expected behaviour |
|---|---|
| Required capability available | The correct tool or Flow is invoked |
| Capability unavailable | The solution follows the approved fallback |
| Invalid input | The call is not made or returns controlled validation |
| Empty result | The worker or Flow explains the approved next step |
| Tool failure | The process does not invent success |
| Wrong tool request | The worker does not call an unrelated capability |
| Repeated request | The action is not duplicated when that would be unsafe |
| Sensitive action | Human approval occurs before execution where required |
- 1Test the worker without the connected capability.
- 2Test the normal successful call.
- 3Test missing required input.
- 4Test an invalid value.
- 5Test a simulated unavailable result where possible.
- 6Confirm the fallback path.
- 7Confirm that the user is not shown raw technical errors.
- 8Confirm that the worker does not invent a successful outcome.
- 9Retest the complete Flow.
- 10Repeat the test after deployment.
Integration review checklist
Complete this before publishing or deploying a connected solution.
- The correct workspace is active.
- The selected model is appropriate for the task.
- The required credential is available.
- No credentials were placed in project content.
- Only required tools are attached.
- Behaviour instructions explain when each tool may be used.
- Every tool has a defined input and expected result.
- Reusable business actions are encapsulated in deterministic Flows.
- Agentic Worker steps reference the intended worker.
- Conversational mode matches the use case.
- HTTP and MCP routes have controlled failure paths.
- Required knowledge bases are attached separately.
- Required guardrails are installed and operational.
- Deployment environments contain only the required resources.
- Successful and failed capability calls have been tested.
- Post-deployment testing has been completed.
Next steps
Integration troubleshooting
Most integration problems are availability, workspace or contract issues.
| Problem | Likely cause | Action |
|---|---|---|
| A model credential is missing | The provider is not configured or not exposed to the workspace | Contact the workspace or partnership administrator |
| The wrong model is being used | An unintended credential or model was selected | Review the worker Model tab |
| An extension is missing | It is not installed or available to the workspace | Ask the administrator to review Extensions |
| A Flow cannot be added as a tool | It is unavailable, unpublished or in another workspace | Confirm the project and publication state |
| A worker does not appear in a Flow step | It has not been published locally or the workspace is wrong | Publish the worker and confirm the workspace |
| The worker calls an unrelated tool | Too many tools are attached or instructions are unclear | Remove unnecessary tools and strengthen usage rules |
| A tool receives the wrong value | Input mapping or field naming is inconsistent | Review the worker contract and Flow variables |
| A capability returns no result | The resource is unavailable or the request is invalid | Follow the approved fallback and review configuration |
| A tool failure is presented as success | The process does not inspect the returned status | Add a controlled decision after the call |
| An MCP or HTTP option is unavailable | The tenant-level resource is not configured | Review the Admin AI and tools configuration |
| The deployment environment is incomplete | Required channel, worker, provider or capability is missing | Add and connect the required resources |
| An integration works in Designer but not after deployment | The environment does not include the same supporting resources | Compare project dependencies with environment wiring |
| A secret appears in a prompt or variable | Credentials were handled through an unsafe field | Remove and rotate the credential, then use secure administration |
