Official vendor OpenAPI document · agent-readyAnalyticsData PipelinesapiKey23 EndpointsREST
For Agents
Use the Amazon AppFlow API to transfer data between SaaS applications and AWS on AWS, with 23 operations covering the full control-plane lifecycle.
Use for: Create a flow to sync Salesforce opportunities to S3, I want to schedule a daily Zendesk-to-Redshift export, List all flows that pull from Slack, Get the execution history for a given flow
Not supported: Does not handle stream processing, ad-hoc SQL queries, or custom ETL transformations beyond field mapping - use for managed SaaS-to-AWS data flows only.
Amazon AppFlow moves data between SaaS applications and AWS services without writing custom integration code. It supports scheduled, event-driven, and on-demand flows, with built-in connectors for Salesforce, Slack, Zendesk, ServiceNow, Marketo, S3, Redshift, and more.
Install Jentic One Beta
Connect the Amazon Appflow to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon Appflow, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Faws-appflow" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Faws-appflow" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Amazon Appflow API.
Create flows that copy records from a SaaS source to S3, Redshift, or another supported destination
Configure connector profiles with OAuth or API key credentials for each SaaS application
Schedule flows on a fixed cadence or trigger them from SaaS events
Apply field-level mapping, filtering, and validation tasks to records in transit
Inspect connector entity schemas before designing field mappings
Track per-execution record counts, error counts, and run status
Use Cases
Patterns agents use Amazon Appflow API for, with concrete tasks.
★ Salesforce-to-S3 nightly sync
Replicate Salesforce objects such as Accounts, Opportunities, and Contacts to an S3 bucket on a nightly schedule for analytics and archival. AppFlow handles connector authentication, incremental record pulls, and CSV or Parquet output formatting without custom ETL code. Initial setup is typically completed in an afternoon per object.
Create a flow named 'salesforce-opps-nightly' that uses the Salesforce connector profile, pulls the Opportunity entity, lands records into the analytics-raw S3 bucket as Parquet, and runs daily at 02:00 UTC.
Event-driven Slack notification ingest
Capture Slack channel messages or app events and stream them into Amazon S3 or Amazon EventBridge for compliance archival or downstream automation. AppFlow's event-triggered flows respond to incoming Slack events in near-real-time so the destination data set is always current. Setup typically takes under a day once OAuth is configured.
Create an event-triggered flow that consumes Slack channel messages from the #engineering channel and lands them in the slack-archive S3 bucket as JSON.
ServiceNow-to-Redshift incident reporting
Move ServiceNow incident records into Amazon Redshift for cross-system reporting alongside other operational data. AppFlow incremental pulls minimise load on the ServiceNow instance, and field mappings let analysts standardise column names before the data lands. Initial wiring is generally completed in a day per ServiceNow table.
Create a flow that pulls the incident table from the ServiceNow connector profile, applies a field mapping that renames sys_id to incident_id, and loads results into the ops_warehouse Redshift cluster on an hourly schedule.
AI agent orchestrating SaaS data movement through Jentic
An analytics agent can spin up new data flows on demand by discovering AppFlow operations through Jentic. The agent searches for the connector and entity it needs, loads the CreateFlow schema, and executes the call with scoped AWS credentials. This turns a multi-step ETL provisioning task into a single agent intent.
Search Jentic for 'create a flow to move Salesforce records into S3', load the CreateFlow schema, and execute it for the Account entity with daily scheduling.
Key Endpoints
23 endpoints — amazon appflow moves data between saas applications and aws services without writing custom integration code.
METHOD
PATH
DESCRIPTION
POST
/create-flow
Create a flow between source and destination connectors
POST
/create-connector-profile
Create a reusable connector profile
POST
/describe-flow
Describe a flow including triggers and tasks
POST
/describe-flow-execution-records
List historical execution records for a flow
POST
/list-flows
List all flows in the account
POST
/describe-connector-entity
Describe the schema of a connector entity
POST
/create-flow
Create a flow between source and destination connectors
POST
/create-connector-profile
Create a reusable connector profile
POST
/describe-flow
Describe a flow including triggers and tasks
POST
/describe-flow-execution-records
List historical execution records for a flow
POST
/list-flows
List all flows in the account
POST
/describe-connector-entity
Describe the schema of a connector entity
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
Amazon Appflow
- AI-Aware (B-)61/100
99
Foundational Compliance63
Developer Experience & Jentic Compatibility38
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
38
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
51%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Amazon AppFlow by hand means creating IAM credentials, picking the right regional host from appflow.{region}.amazonaws.com, signing every request with AWS SigV4, and adding your own retry handling. Through Jentic you install once, import Amazon AppFlow from the API Directory, store the AWS access key once, and your agent calls it.
Permission scoping
Amazon AppFlow carries the flow and connector target in the request body rather than the URL path, so limit the agent to the operations it needs, such as create-flow, describe-flow, or list-flows. You choose the operations it may call, so destructive ones like deleting a flow or a connector profile are not included unless you add them.
Credential isolation
Your AWS access key for Amazon AppFlow is stored once, encrypted, by your own Jentic One instance and signed with SigV4 at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a flow to move Salesforce records into S3' or 'list execution records for a flow', and Jentic returns the matching Amazon AppFlow operation with its input schema so the agent calls the right endpoint without browsing the AWS service reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Amazon Appflow API through Jentic.
What authentication does the Amazon AppFlow API use?
The Amazon AppFlow API uses AWS Signature Version 4 (HMAC) request signing with IAM-issued credentials, the same scheme as every AWS service API. Jentic's your Jentic One instance stores those AWS credentials encrypted in the vault, generates short-lived signed requests at execution time, and never passes raw access keys into the agent's context.
Can I create a flow to sync salesforce opportunities to s3 with the Amazon AppFlow API?
Yes - the Amazon AppFlow API exposes 23 operations including the actions needed for that scenario. Use the operations listed in the key endpoints section as the starting point, then chain calls as needed for your workflow.
What are the rate limits for the Amazon AppFlow API?
AWS applies per-account, per-region request rate limits to the Amazon AppFlow control plane. Specific limits are not encoded in the OpenAPI spec; consult the AWS service quotas console for the Amazon AppFlow entry, and design retries with exponential backoff to absorb throttling responses.
How do I create a flow to move Salesforce records into S3 through Jentic?
Run pip install jentic, then call client.search('create a flow to move Salesforce records into S3') to discover the Amazon AppFlow operations that match. Load the schema for the chosen operation with client.load(...) and execute it with client.execute(...). Jentic handles AWS request signing automatically against the credentials stored in your Jentic One instance.
Is the Amazon AppFlow API free to call?
AWS does not charge for control-plane API calls themselves on most Amazon AppFlow operations, but the underlying resources you create or operate (fleets, queries, deployments, and so on) incur usage charges according to the Amazon AppFlow pricing page. Refer to the AWS pricing page for the service to estimate cost.
Which operations should an agent call first when working with the Amazon AppFlow API?
For most workflows, agents should start by listing existing resources to understand the current state, then call the create or update operation that matches the intent. The endpoints listed under Key Endpoints in the catalog give a ranked starting set.
Can I limit what my agent is allowed to do with the AWS AppFlow API?
Yes. Because Jentic One is self-hosted, you set the rules that decide which AWS AppFlow operations and which AWS credentials your agent can use, so you can allow only the calls it needs, such as create-flow, describe-flow, or list-flows. AppFlow carries the flow and connector target in the request body rather than the URL path, so scoping is done per operation rather than per resource path. Destructive operations like deleting a flow or a connector profile are excluded unless you explicitly add them to the set the agent may call.
GET STARTED