How to connect Amazon S3 and Kintone
Create a New Scenario to Connect Amazon S3 and Kintone
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Amazon S3, triggered by another scenario, or executed manually (for testing purposes). In most cases, Amazon S3 or Kintone will be your first step. To do this, click "Choose an app," find Amazon S3 or Kintone, and select the appropriate trigger to start the scenario.

Add the Amazon S3 Node
Select the Amazon S3 node from the app selection panel on the right.


Amazon S3

Configure the Amazon S3
Click on the Amazon S3 node to configure it. You can modify the Amazon S3 URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Kintone Node
Next, click the plus (+) icon on the Amazon S3 node, select Kintone from the list of available apps, and choose the action you need from the list of nodes within Kintone.


Amazon S3
⚙
Kintone

Authenticate Kintone
Now, click the Kintone node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Kintone settings. Authentication allows you to use Kintone through Latenode.
Configure the Amazon S3 and Kintone Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Amazon S3 and Kintone Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙
Kintone
Trigger on Webhook
⚙

Amazon S3
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Amazon S3, Kintone, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Amazon S3 and Kintone integration works as expected. Depending on your setup, data should flow between Amazon S3 and Kintone (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Amazon S3 and Kintone
Amazon S3 + Kintone + Google Sheets: When a new file is uploaded to Amazon S3, it triggers the creation of a new record in Kintone, archiving the S3 data. The details of this archive event, including the file name and timestamp, are then logged in a Google Sheets spreadsheet for audit purposes.
Kintone + Amazon S3 + Slack: When a record's status is updated in Kintone, this triggers the retrieval of related files from Amazon S3. These files are then used to compose a message that is sent to a designated Slack channel, notifying the team about the status change and providing access to the associated files.
Amazon S3 and Kintone integration alternatives

About Amazon S3
Automate S3 file management within Latenode. Trigger flows on new uploads, automatically process stored data, and archive old files. Integrate S3 with your database, AI models, or other apps. Latenode simplifies complex S3 workflows with visual tools and code options for custom logic.
Similar apps
Related categories
About Kintone
Integrate Kintone into Latenode to automate custom application workflows. Sync data, trigger actions, and manage processes without code. Extend Kintone's capabilities with Latenode's visual builder, JavaScript functions, and AI tools to automate data validation, reporting, and notifications. Scale efficiently and only pay for what you use.
Related categories
See how Latenode works
FAQ Amazon S3 and Kintone
How can I connect my Amazon S3 account to Kintone using Latenode?
To connect your Amazon S3 account to Kintone on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Amazon S3 and click on "Connect".
- Authenticate your Amazon S3 and Kintone accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically back up Kintone data to Amazon S3?
Yes, you can! Latenode simplifies automated backups with its visual editor. Schedule backups and ensure data safety with flexible logic and scalable infrastructure, no coding required.
What types of tasks can I perform by integrating Amazon S3 with Kintone?
Integrating Amazon S3 with Kintone allows you to perform various tasks, including:
- Automatically uploading files from Kintone to Amazon S3.
- Triggering Kintone record updates based on new Amazon S3 file uploads.
- Archiving old Kintone records as compressed files in Amazon S3.
- Generating reports from Amazon S3 data and storing them in Kintone.
- Creating a searchable archive of Kintone data within Amazon S3.
What Amazon S3 operations are supported within Latenode?
Latenode supports a wide range of Amazon S3 operations, including file uploads, downloads, listing buckets, and managing object metadata.
Are there any limitations to the Amazon S3 and Kintone integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Large file transfers might be subject to Amazon S3 and Kintone API rate limits.
- Complex data transformations may require JavaScript steps for advanced manipulation.
- Real-time synchronization depends on API availability and may not be instantaneous.