clients/client-appflow/README.md
AWS SDK for JavaScript Appflow Client for Node.js, Browser and React Native.
<p>Welcome to the Amazon AppFlow API reference. This guide is for developers who need detailed information about the Amazon AppFlow API operations, data types, and errors. </p> <p>Amazon AppFlow is a fully managed integration service that enables you to securely transfer data between software as a service (SaaS) applications like Salesforce, Marketo, Slack, and ServiceNow, and Amazon Web Services like Amazon S3 and Amazon Redshift. </p> <p>Use the following links to get started on the Amazon AppFlow API:</p> <ul> <li> <p> <a href="https://docs.aws.amazon.com/appflow/1.0/APIReference/API_Operations.html">Actions</a>: An alphabetical list of all Amazon AppFlow API operations.</p> </li> <li> <p> <a href="https://docs.aws.amazon.com/appflow/1.0/APIReference/API_Types.html">Data types</a>: An alphabetical list of all Amazon AppFlow data types.</p> </li> <li> <p> <a href="https://docs.aws.amazon.com/appflow/1.0/APIReference/CommonParameters.html">Common parameters</a>: Parameters that all Query operations can use.</p> </li> <li> <p> <a href="https://docs.aws.amazon.com/appflow/1.0/APIReference/CommonErrors.html">Common errors</a>: Client and server errors that all operations can return.</p> </li> </ul> <p>If you're new to Amazon AppFlow, we recommend that you review the <a href="https://docs.aws.amazon.com/appflow/latest/userguide/what-is-appflow.html">Amazon AppFlow User Guide</a>.</p> <p>Amazon AppFlow API users can use vendor-specific mechanisms for OAuth, and include applicable OAuth attributes (such as <code>auth-code</code> and <code>redirecturi</code>) with the connector-specific <code>ConnectorProfileProperties</code> when creating a new connector profile using Amazon AppFlow API operations. For example, Salesforce users can refer to the <a href="https://help.salesforce.com/articleView?id=remoteaccess_authenticate.htm"> <i>Authorize Apps with OAuth</i> </a> documentation.</p>To install this package, use the CLI of your favorite package manager:
npm install @aws-sdk/client-appflowyarn add @aws-sdk/client-appflowpnpm add @aws-sdk/client-appflowThe AWS SDK is modulized by clients and commands.
To send a request, you only need to import the AppflowClient and
the commands you need, for example ListFlowsCommand:
// ES5 example
const { AppflowClient, ListFlowsCommand } = require("@aws-sdk/client-appflow");
// ES6+ example
import { AppflowClient, ListFlowsCommand } from "@aws-sdk/client-appflow";
To send a request:
send operation on the client, providing the command object as input.const client = new AppflowClient({ region: "REGION" });
const params = { /** input parameters */ };
const command = new ListFlowsCommand(params);
We recommend using the await operator to wait for the promise returned by send operation as follows:
// async/await.
try {
const data = await client.send(command);
// process data.
} catch (error) {
// error handling.
} finally {
// finally.
}
You can also use Promise chaining.
client
.send(command)
.then((data) => {
// process data.
})
.catch((error) => {
// error handling.
})
.finally(() => {
// finally.
});
The aggregated client class is exported from the same package, but without the "Client" suffix.
Appflow extends AppflowClient and additionally supports all operations, waiters, and paginators as methods.
This style may be familiar to you from the AWS SDK for JavaScript v2.
If you are bundling the AWS SDK, we recommend using only the bare-bones client (AppflowClient).
More details are in the blog post on
modular packages in AWS SDK for JavaScript.
import { Appflow } from "@aws-sdk/client-appflow";
const client = new Appflow({ region: "REGION" });
// async/await.
try {
const data = await client.listFlows(params);
// process data.
} catch (error) {
// error handling.
}
// Promises.
client
.listFlows(params)
.then((data) => {
// process data.
})
.catch((error) => {
// error handling.
});
// callbacks (not recommended).
client.listFlows(params, (err, data) => {
// process err and data.
});
When the service returns an exception, the error will include the exception information, as well as response metadata (e.g. request id).
try {
const data = await client.send(command);
// process data.
} catch (error) {
const { requestId, cfId, extendedRequestId } = error.$metadata;
console.log({ requestId, cfId, extendedRequestId });
/**
* The keys within exceptions are also parsed.
* You can access them by specifying exception names:
* if (error.name === 'SomeServiceException') {
* const value = error.specialKeyInException;
* }
*/
}
See also docs/ERROR_HANDLING.
Please use these community resources for getting help. We use GitHub issues for tracking bugs and feature requests, but have limited bandwidth to address them.
aws-sdk-js
on AWS Developer Blog.aws-sdk-js.To test your universal JavaScript code in Node.js, browser and react-native environments, visit our code samples repo.
This client code is generated automatically. Any modifications will be overwritten the next time the @aws-sdk/client-appflow package is updated.
To contribute to client you can check our generate clients scripts.
This SDK is distributed under the Apache License, Version 2.0, see LICENSE for more information.
Command API Reference / Input / Output
</details> <details> <summary> CreateConnectorProfile </summary>Command API Reference / Input / Output
</details> <details> <summary> CreateFlow </summary>Command API Reference / Input / Output
</details> <details> <summary> DeleteConnectorProfile </summary>Command API Reference / Input / Output
</details> <details> <summary> DeleteFlow </summary>Command API Reference / Input / Output
</details> <details> <summary> DescribeConnector </summary>Command API Reference / Input / Output
</details> <details> <summary> DescribeConnectorEntity </summary>Command API Reference / Input / Output
</details> <details> <summary> DescribeConnectorProfiles </summary>Command API Reference / Input / Output
</details> <details> <summary> DescribeConnectors </summary>Command API Reference / Input / Output
</details> <details> <summary> DescribeFlow </summary>Command API Reference / Input / Output
</details> <details> <summary> DescribeFlowExecutionRecords </summary>Command API Reference / Input / Output
</details> <details> <summary> ListConnectorEntities </summary>Command API Reference / Input / Output
</details> <details> <summary> ListConnectors </summary>Command API Reference / Input / Output
</details> <details> <summary> ListFlows </summary>Command API Reference / Input / Output
</details> <details> <summary> ListTagsForResource </summary>Command API Reference / Input / Output
</details> <details> <summary> RegisterConnector </summary>Command API Reference / Input / Output
</details> <details> <summary> ResetConnectorMetadataCache </summary>Command API Reference / Input / Output
</details> <details> <summary> StartFlow </summary>Command API Reference / Input / Output
</details> <details> <summary> StopFlow </summary>Command API Reference / Input / Output
</details> <details> <summary> TagResource </summary>Command API Reference / Input / Output
</details> <details> <summary> UnregisterConnector </summary>Command API Reference / Input / Output
</details> <details> <summary> UntagResource </summary>Command API Reference / Input / Output
</details> <details> <summary> UpdateConnectorProfile </summary>Command API Reference / Input / Output
</details> <details> <summary> UpdateConnectorRegistration </summary> </details> <details> <summary> UpdateFlow </summary> </details>