sisincube
Integrations Support Privacy Terms
AI Workflow Architect

Support & How to Use

Everything you need to describe a workflow clearly, understand the Architecture Readiness Preview, work with a Complete Automation Blueprint and resolve common ChatGPT or account-connection issues.

ChatGPT integration Workflow-first planning Existing-account access
01 · Connect and use

Use AI Workflow Architect in ChatGPT

If AI Workflow Architect is available in your ChatGPT environment, select it for the conversation and describe the workflow you want to improve. ChatGPT can pass the relevant workflow context to AI Workflow Architect and return the structured result in the conversation.

Availability during review: during platform review or pre-release testing, access may be limited to authorised testers or a manually connected MCP server. This page does not imply that a public ChatGPT listing is currently available.
02 · Describe the workflow

Start with the process, not the software

You do not need a finished process map or technical specification. Explain what starts the workflow, who takes part, which systems are involved, what happens today and where the process becomes slow, unclear or unreliable.

Example prompt

Help me architect our client onboarding workflow. A signed proposal triggers a handoff from Sales to Operations. Operations creates the project workspace, requests assets and access, and follows up when information is missing. Delivery cannot start until everything is ready. We need clearer ownership, fewer manual chases and a future-state plan that shows what can be automated safely.
03 · Helpful context

What improves the result

Where relevant, include:

  • the trigger and intended outcome;
  • the roles responsible for each stage;
  • the tools, records and information used;
  • workflow volume, frequency and time sensitivity;
  • where people wait, chase, copy, approve or re-enter information;
  • common exceptions and failure paths;
  • what “ready”, “approved” or “complete” means;
  • security, compliance or human-review requirements;
  • known technical, budget or implementation constraints.

Use roles rather than individual names wherever possible. Include only the operational detail needed to understand the workflow.

04 · Readiness preview

What the Architecture Readiness Preview returns

The preview is an early assessment of whether the workflow is sufficiently understood for architecture work. It may identify:

  • the likely workflow problem and desired outcome;
  • missing context or unresolved decisions;
  • unclear ownership and handoff risks;
  • process rules that should be stabilised first;
  • areas suitable for automation and areas that should stay human;
  • controls, exception paths or data requirements that need clarification;
  • the next questions to answer before creating a complete blueprint.
05 · Complete blueprint

What the Complete Automation Blueprint returns

When an existing entitlement is recognised and enough workflow context is available, AI Workflow Architect can create a more detailed implementation reference. Depending on the workflow, it may include:

  • a current-state summary and future-state workflow;
  • automated steps, human decisions and named ownership roles;
  • business rules, controls and approval points;
  • exception paths, failure handling and escalation needs;
  • data, system and integration requirements;
  • security, auditability and operational safeguards;
  • an implementation sequence and dependency notes;
  • acceptance criteria and questions for the delivery team.
06 · Follow-up prompts

Keep refining the plan in context

Use the same conversation to test assumptions and make the blueprint more useful. For example:

Which steps should remain human, and why?
Show the exception path when required client information is still missing after two reminders.
What controls would reduce the risk of an automation moving a project forward too early?
Turn this blueprint into a phased implementation sequence for a small operations team.
What should the implementation team validate before selecting tools?
07 · Account and access

Connect an existing entitlement when asked

The Architecture Readiness Preview and Complete Automation Blueprint may have different access requirements. When an authenticated blueprint feature is requested, ChatGPT may present an account-connection step.

Use that step to sign in to the appropriate AI Workflow Architect account. If an existing entitlement is recognised, the assistant can continue with the entitled feature. Do not paste account passwords, access tokens or private credentials into the conversation.

This integration page and support flow do not provide checkout, pricing or an upgrade action. If access is not recognised, contact support with the account email or organisation name used for AI Workflow Architect.
08 · Safe use

Minimise sensitive information

Describe workflows using roles, generic system names and representative examples wherever possible. Do not submit passwords, API keys, access tokens, payment details or authentication credentials. Avoid personal, confidential or regulated data unless it is necessary and you are authorised to provide it.

Treat generated architecture as professional planning material that still requires validation by the people responsible for operations, security, compliance and implementation. Read the AI Workflow Architect Privacy Policy for details about stored projects and generated outputs.

09 · Troubleshooting

If the experience does not work as expected

Start a new ChatGPT conversation

If the tool response stalls or the conversation has conflicting instructions, start a fresh chat, select AI Workflow Architect again and provide a concise workflow description.

Check that the integration is available

Confirm that AI Workflow Architect is enabled in the ChatGPT environment or review setup you are using. Availability may differ during testing and platform review.

Reconnect the correct account

If a Complete Automation Blueprint is unavailable despite existing access, repeat the account-connection step and confirm you are using the expected AI Workflow Architect account or organisation.

Add missing workflow context

If the preview remains inconclusive, answer the missing-context questions before requesting a blueprint. A workflow with unclear ownership or completion rules may not yet be ready to architect.

Still stuck?

Email sisi@sisincube.com with a screenshot, the approximate time of the issue and a short description of the step that failed. Remove confidential workflow details unless they are required to diagnose the problem.

10 · Contact

AI Workflow Architect support

Support contact: sisi@sisincube.com
Publisher/operator: The UGC Playbook LTD trading as sisincube
Website: sisincube.com

On this page Connect and use Describe a workflow Helpful context Readiness preview Complete blueprint Follow-up prompts Account access Safe use Troubleshooting Contact
sisincube
AI Workflow Architect · Published and operated by The UGC Playbook LTD trading as sisincube
IntegrationsSupport & How to usePrivacyTermsSite privacy