Quick Integration Actions

Q&A
, ,
1

Hey everyone, first post here. I’m currently having a problem when trying to apply my integrations on Amazon Quick. Any insights or help would be greatly appreciated.

The Problem

There’s a disconnect between the configured Integration “Actions” and the tools actually available to Quick agents and Flows .
The “Actions” seem to be not available when building “Flows” and “Agents” despite the “Actions” being available in the integrations section.
The agents cannot perform basic S3 operations like uploading files despite being specifically designed and authorized for S3 document management.

Impact

  • Cannot upload documents to S3 buckets

  • S3 Document Manager agent is effectively non-functional for its primary purpose

Steps Already Attempted

  1. Verified S3 Connector configuration

  2. Confirmed target bucket name

  3. Attempted to use PutObject functionality

  4. Troubleshot tool availability

2

Hi @AlejandroT - Welcome to the community!

The disconnect you’re experiencing typically stems from these key factors:*1. *Action Connector Configuration Requirements****
For S3 operations like PutObject (file uploads), Amazon S3 action connectors must be created through the admin console, not the regular integrations interface. The S3 integration you see in the regular integrations section is primarily for data ingestion and knowledge base creation, not for action execution.*2. *Administrative Prerequisites****
Action connectors require specific administrative setup:

  • Administrators must configure action connectors before they become available to Flows creators

  • Only connectors configured by administrators will be accessible for use in Flow creation

  • AWS service action connectors (including S3) can only be created through the Amazon Quick admin console

*3. *Permission and Access Requirements****

  • You need administrative access to your Amazon Quick account

  • An IAM role with necessary permissions for the connector you want to create

  • Access to the Amazon Quick admin console

Resolution Steps

Step 1: Create S3 Action Connector via Admin Console

  1. Sign in to AWS using administrative credentials

  2. Navigate to Amazon Quick service

  3. Choose Admin to access the admin console

  4. In left navigation, choose Permissions → AWS action connectors

  5. Choose New action in the upper right corner

  6. Select Amazon S3 from available AWS services

  7. Configure with:

    • Descriptive name for your connector

    • Role ARN for IAM role with S3 permissions

    • Required S3 permissions: s3:PutObject, s3:GetObject, s3:ListBucket, etc.

Step 2: Configure Sharing Permissions

  1. Choose Share to add users/groups who can access the connector

  2. Select appropriate permission level:

    • Owner: Full permissions to share, edit, and delete

    • User: Permission to use connector in automation workflows

Step 3: Verify Availability in Flows/Agents
After creating the action connector:

  1. Sign in to Amazon Quick as a regular user

  2. Navigate to Integrations or when creating Flows/Agents

  3. Verify the S3 action connector appears in available actions

Important Distinctions

S3 Data Integration vs S3 Action Connector:

  • S3 Data Integration (regular integrations): For creating knowledge bases from S3 content

  • S3 Action Connector (admin console): For performing S3 operations like upload, download, delete files

Based on the compatibility matrix, Amazon S3 action connectors are only supported in Quick Automate workflows, not in Flows or Chat Agents. This explains why your S3 Document Manager agent cannot perform S3 operations - S3 actions are specifically restricted to automation workflows only.

Recommended Solution

Since S3 actions aren’t available in Flows or Agents, consider these alternatives:

  1. Use Quick Automate instead of Flows for S3 file operations

  2. Create automation workflows that handle S3 document management

  3. Integrate automations with agents through supported connectors that do work with agents (like Slack, Teams, etc.)

Thanks,

Raj Kavuda

2 Likes
3

Hi @RajKavuda,

Thank you very much for the detailed explanation. Your insights into the distinction between the S3 Data Integration and the S3 Action Connector, as well as the administrative setup, are very clear.

I understand that S3 Action Connectors are currently limited to Quick Automate. The challenge I’m facing is that my use case isn’t for a scheduled or recurring task, but rather for an on-demand action triggered directly from the Quick chat agent. The goal is to allow a user to upload a file to an S3 bucket during their chat session.

Given that “Actions” are not currently available for “Chat Agents” or “Flows,” I have two follow-up questions for you and the broader community:

  1. Is there any available workaround or alternative integration method that would allow us to achieve this on-demand file upload from the chat agent right now?

  2. Is there a projected date or an item on the product roadmap for integrating “Actions” (like S3 operations) with “Chat Agents” and “Flows”?

Any guidance on this would be extremely helpful as it’s a key function for the agent we are developing.

Thanks again for your support.

Best regards, Alejandro