The Lyftron Provider for Asana offers the most natural way to access Asana data from Lyftron with ease and also enables to connect with BI, MDM & ML tools, Data warehouses, Databases and other SAAS based applications with zero code and zero infrastructure requirements. The provider wraps the complexity of accessing Asana data into easy-to-integrate relational fully managed ANSI Sql format. Make faster and better business decisions with Lyftron’s Asana data provider and automatically build your data migration pipelines in minutes, not months
The provider hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.
- Comprehensive Delta load mechanism.
- Real-time access to Asana.
- Comprehensive full support of ANSI Sql to query data with ease.
- Collaborative query processing.
The user must have credentials for Asana, Lyftron and your destination data warehouse, lake or database to perform the data pipeline operation with Lyftron
Establishing a Connection with Lyftron's Quickstart Steps
Create your Asana connection with Lyftron by following the 5 easy steps show below:
Step1. Add your connection
Click on Connect section on the left panel → Click on Add Connection button
Step2. Select your connector
In the connector selection panel, search and click Asana for your connection
Step3. Enter your connection details
In the Connection String section enter the values of the below parameters. The following connection string is required to establish Asana connection with Lyftron."InitiateOAuth=GETANDREFRESH;OAuthClientId=YourClientId;OAuthClientSecret=YourClientSecret;CallbackURL='http://localhost:33333'"
|Connection Name||Enter your connection details||Required|
|OAuthClientId||Your Asana OAuthClientId||Required|
|OAuthClientSecret||Your Asana OAuthClientSecret||Required|
|Logfile**||Use the logfile option to debug your job and provide your connection name to generate the log file. [ConnectionConfigurationPath]\Connection_name_log.tx||Optional|
|Verbosity**||Choose verbosity 1-5 based on the severity of debugging||Optional|
** For more information, check the Lyftron logging and debugging section.
If you want more detailed information about how to establish a connection with Lyftron, click on Lyftron Connection Quick Start guide.
Step4. Test your connection
Once you are done entering your connection details, simply click on the Test Connection button to test the connectivity. In case your connection fails, add Logfile and Verbosity parameters and check the Lyftron logging and debugging section, to debug the error.
Step5. Save your connection
This section shows the available API objects and provides more information on executing SQL to Asana APIs.
- The provider models Asana entities as relational views, allowing you to write SQL to query Asana data.
- Stored procedures allow you to execute operations to Asana, including retrieving the access token and keeping it refreshed in OAuth 2.0.
- Live connectivity to these objects means any changes to your Asana account are immediately reflected when using the provider.
- IncludeCustomFields connection property allows you to retrieve custom fields for Tasks view. Set this property to True, to enable this feature.
Views are composed of columns and pseudo columns. Views are similar to tables in the way that data is represented; however, views do not support updates. Entities that are represented as views are typically read-only entities. Often, a stored procedure is available to update the data if such functionality is applicable to the data source.
Queries can be executed against a view as if it were a normal table, and the data that comes back is similar in that regard.
|Attachments||Views||To view the attachments in the tasks|
|Events||Views||To view the events in projects and tasks|
|ProjectMemberships||Views||To view the memberships in the Project|
|Projects||Views||To view the Projects|
|ProjectStatuses||Views||A project status is an update on the progress of a particular project, and is sent out to all project followers when created.|
|Sections||Views||A section is a subdivision of a project that groups tasks together.|
|Stories||Views||A story represents an activity associated with an object in the Asana system. Stories are generated by the system whenever users take actions such as creating or assigning tasks, or moving tasks between projects.|
|SubTasks||Views||To view the subtasks|
|Tags||Views||A tag is a label that can be attached to any task in Asana. It exists in a single workspace.|
|Tasks||Views||To view the tasks|
|TaskStatuses||Views||Get task count of a project|
|TeamMembership||Views||To represents a users connection to a team.|
|Teams||Views||A team is used to group related projects and people together within an organization. Each project in an organization is associated with a team.|
|Users||Views||To view the users details|
|UserTaskList||Views||Generated schema file.|
|WorkspaceMembership||Views||To determines if user is a member of a workspace.|
|Workspaces||Views||A workspace is the highest-level organizational unit in Asana. All projects and tasks have an associated workspace.|