Asana Connector for SQL Server
In this article you will learn how to integrate Asana data in SQL Server
without coding in just a few clicks (live / bi-directional connection to Asana).
Read and write data related to Tasks, Projects, Workspaces, Portfolios, TimeEntries, Memberships and more..
Using Asana Connector you will be able to connect, read, and write data from within SQL Server. Follow the steps below to see how we would accomplish that.
Download
Documentation
The driver mentioned above is part of ODBC PowerPack which is a collection of high-performance Drivers for various API data source (i.e. REST API, JSON, XML, CSV, Amazon S3 and many more). Using familiar SQL query language you can make live connections and read/write data from API sources or JSON / XML / CSV Files inside SQL Server (T-SQL) or your favorite Reporting (i.e. Power BI, Tableau, Qlik, SSRS, MicroStrategy, Excel, MS Access), ETL Tools (i.e. Informatica, Talend, Pentaho, SSIS). You can also call our drivers from programming languages such as JAVA, C#, Python, PowerShell etc.
If you are new to ODBC and ZappySys ODBC PowerPack then check the following links to get started.
|
Connect to Asana in other apps
|
Video Tutorial - Integrate Asana data in SQL Server
This video covers following and more so watch carefully. After watching this video follow the steps described in this article.
- How to download / install required driver for Asana integration in SQL Server
- How to configure connection for Asana
- Features about API Driver (Authentication / Query Language / Examples / Driver UI)
- Using Asana Connection in SQL Server
Create Data Source in ZappySys Data Gateway based on API Driver
-
Download and install ZappySys ODBC PowerPack.
-
Search for gateway in start menu and Open ZappySys Data Gateway:
-
Go to Users Tab to add our first Gateway user. Click Add; we will give it a name tdsuser and enter password you like to give. Check Admin option and click OK to save. We will use these details later when we create linked server:
-
Now we are ready to add a data source. Click Add, give data source a name (Copy this name somewhere, we will need it later) and then select Native - ZappySys API Driver. Finally, click OK. And it will create the Data Set for it and open the ZS driver UI.
AsanaDSN
-
When the Configuration window appears give your data source a name if you haven't done that already,
then select "Asana" from the list of Popular Connectors. If "Asana" is not present
in the list, then click "Search Online" and download it. Then set the path to the location where you
downloaded it. Finally, click Continue >> to proceed with configuring the DSN:
AsanaDSN
Asana
-
Now it's time to configure the Connection Manager. Select Authentication Type,
e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one).
More info is available in the Authentication section.
Steps how to get and use Asana credentials
Here is how to obtain a Personal Access Token (PAT) in Asana:
-
Open My apps in Asana portal
and click Create new token button:
-
Once a popup opens, name your new token:
-
Then click Copy button to copy the token:
-
Now go to SSIS package or ODBC data source and use this token in Personal Access Token authentication configuration.
-
Choose Default Workspace and Default Project to work with.
-
Click Test Connection to confirm the connection is working.
-
Done! Now you are ready to use Asana Connector!
Fill in all required parameters and set optional parameters if needed:
AsanaDSN
Asana
Personal Access Token [Http]
https://app.asana.com/api/1.0
Steps how to get and use Asana credentials
Here is how to register an OAuth app in Asana:
-
Open My apps in Asana portal
and click Create new app button:
-
Once a popup opens, name your app and check two options, and click Create app button:
-
Then copy Client ID and Client secret and save them in a file (we will need them for authentication):
-
Continue by selecting OAuth menu item on your left and click Add redirect URL button (you can have your own or use
https://zappysys.com/oauth
):
-
Proceed by clicking on the Manage distribution section on your left.
-
Then specify workspaces your app needs to access (use Any workspace to access them all):
-
Once you do that, click Save changes button.
-
Now go to SSIS package or ODBC data source and use
Client ID, Client Secret, and Redirect URL in OAuth app authentication configuration.
-
When you are done with that, click Generate Token button to generate Access and Refresh Tokens.
-
Choose Default Workspace and Default Project to work with.
-
Click Test Connection to confirm the connection is working.
-
Done! Now you are ready to use Asana Connector!
Fill in all required parameters and set optional parameters if needed:
AsanaDSN
Asana
OAuth app [OAuth]
https://app.asana.com/api/1.0
-
Once the data source has been configured, you can preview data. Select the Preview tab and use settings similar to the following to preview data:
-
Click OK to finish creating the data source.
Read data in SQL Server from the ZappySys Data Gateway
-
To read the data in SQL Server the first thing you have to do is create a Linked Server. Go to SQL Server Management Studio and configure it in a similar way:
-
Then click on Security option and configure username we created in ZappySys Data Gateway in one of the previous steps:
-
Optional: Under the Server Options, Enable RPC and RPC Out and Disable Promotion of Distributed Transactions(MSDTC).
You need to enable RPC Out if you plan to use EXEC(...) AT [MY_LINKED_SERVER_NAME]
rather than OPENQUERY.
If don't enabled it, you will encounter the Server 'MY_LINKED_SERVER_NAME' is not configured for RPC
error.
Query Example:
EXEC('Select * from Products') AT [MY_LINKED_SERVER_NAME]
If you plan to use 'INSERT INTO...EXEC(....) AT [MY_LINKED_SERVER_NAME]'
in that case you need to Disable Promotion of Distributed Transactions(MSDTC).
If don't disabled it, you will encounter the The operation could not be performed because OLE DB provider "SQLNCLI11" for linked server "MY_LINKED_SERVER_NAME" was unable to begin a distributed transaction.
error.
Query Example:
Insert Into dbo.Products
EXEC('Select * from Products') AT [MY_LINKED_SERVER_NAME]
-
Finally, open a new query and execute a query we saved in one of the previous steps:
SELECT * FROM OPENQUERY([MY_LINKED_SERVER_NAME], 'SELECT * FROM Products');
Create Linked Server using Code
In previous section you saw how to create a Linked Server from UI. You can do similar action by code too (see below). Run below script after changing necessary parameters. Assuming your Data Source name on ZappySys Data Gateway UI is 'AsanaDSN'
USE [master]
GO
--///////////////////////////////////////////////////////////////////////////////////////
--Run below code in SSMS to create Linked Server and use ZappySys Drivers in SQL Server
--///////////////////////////////////////////////////////////////////////////////////////
//Replace YOUR_GATEWAY_USER, YOUR_GATEWAY_PASSWORD
//Replace localhost with IP/Machine name if ZappySys Gateway Running on different machine other than SQL Server
//Replace Port 5000 if you configured gateway on a different port
--1. Configure your gateway service as per this article https://zappysys.com/links?id=10036
--2. Make sure you have SQL Server Installed. You can download FREE SQL Server Express Edition from here if you dont want to buy Paid version https://www.microsoft.com/en-us/sql-server/sql-server-editions-express
--Uncomment below if you like to drop linked server if it already exists
--EXEC master.dbo.sp_dropserver @server=N'LS_AsanaDSN', @droplogins='droplogins'
--3. Create new linked server
EXEC master.dbo.sp_addlinkedserver
@server = N'LS_AsanaDSN' --Linked server name (this will be used in OPENQUERY sql
, @srvproduct=N''
---- For MSSQL 2012,2014,2016 and 2019 use below (SQL Server Native Client 11.0)---
, @provider=N'SQLNCLI11'
---- For MSSQL 2022 or higher use below (Microsoft OLE DB Driver for SQL Server)---
--, @provider=N'MSOLEDBSQL'
, @datasrc=N'localhost,5000' --//Machine / Port where Gateway service is running
, @provstr=N'Network Library=DBMSSOCN;'
, @catalog=N'AsanaDSN' --Data source name you gave on Gateway service settings
--4. Attach gateway login with linked server
EXEC master.dbo.sp_addlinkedsrvlogin
@rmtsrvname=N'LS_AsanaDSN' --linked server name
, @useself=N'False'
, @locallogin=NULL
, @rmtuser=N'YOUR_GATEWAY_USER' --enter your Gateway user name
, @rmtpassword='YOUR_GATEWAY_PASSWORD' --enter your Gateway user's password
GO
--5. Enable RPC OUT (This is Optional - Only needed if you plan to use EXEC(...) AT YourLinkedServerName rather than OPENQUERY
EXEC sp_serveroption 'LS_AsanaDSN', 'rpc', true;
EXEC sp_serveroption 'LS_AsanaDSN', 'rpc out', true;
--Disable MSDTC - Below needed to support INSERT INTO from EXEC AT statement
EXEC sp_serveroption 'LS_AsanaDSN', 'remote proc transaction promotion', false;
--Increase query timeout if query is going to take longer than 10 mins (Default timeout is 600 seconds)
--EXEC sp_serveroption 'LS_AsanaDSN', 'query timeout', 1200;
GO
Firewall settings
So far we have assumed that Gateway is running on the same machine as SQL Server. However there will be a case when ZappySys ODBC PowerPack is installed on a different machine than SQL Server. In such case you may have to perform additional Firewall configurations. On most computers firewall settings wont allow outside traffic to ZappySys Data Gateway. In such case perform following steps to allow other machines to connect to Gateway.
Method-1 (Preferred)
If you are using newer version of ZappySys Data Gateway then adding firewall rule is just a single click.
- Search for gateway in start menu and open ZappySys Data Gateway.
- Go to Firewall Tab and click Add Firewall Rule button like below. This will create Firewall rule to all Inbound Traffic on Port 5000 (Unless you changed it).
Method-2
Here is another way to add / edit Inbound Traffic rule in windows firewall. Use below method if you choose to customize your rule (for advanced users).
- Search for Windows Firewall Advanced Security in start menu.
- Under Inbound Rules > Right click and click [New Rule] >> Click Next
- Select Port on Rule Type >> Click Next
- Click on TCP and enter port number under specified local port as 5000 (use different one if you changed Default port) >> Click Next
- Select Profile (i.e. Private, Public) >> Click Next
- Enter Rule name [i.e. ZappySys Data Gateway – Allow Inbound ] >> Click Next
- Click OK to save the rule
OPENQUERY vs EXEC (handling larger SQL text)
So far we have seen examples of using OPENQUERY. It allows us to send pass-through query at remote server. The biggest limitation of OPENQUERY is it doesn't allow you to use variables inside SQL so often we have to use unpleasant looking dynamic SQL (Lots of tick, tick …. and escape hell). Well there is good news. With SQL 2005 and later you can use EXEC(your_sql) AT your_linked_server
syntax .
Disadvantage of EXEC AT is you cannot do SELECT INTO like OPENQUERY. Also you cannot perform JOIN like below in EXEC AT
SELECT a.* FROM OPENQUERY([ls_AsanaDSN],'select * from Customers') a
JOIN OPENQUERY([ls_AsanaDSN],'select * from Orders') b ON a.CustomerId=b.CustomerId;
However you can always do
INSERT INTO SomeTable EXEC(…) AT your_linked_server
. So table must exists when you do that way.
Here is how to use it. To use
EXEC(..) AT {linked-server}
you must turn on
RPC OUT
option. Notice how we used variable in SQL to make it dynamic. This is much cleaner than previous approach we saw.
USE [master]
GO
--Replace YOUR_GATEWAY_USER, YOUR_GATEWAY_PASSWORD
--Replace localhost with IP/Machine name if ZappySys Gateway Running on different machine other than SQL Server
--Create new linked server
EXEC master.dbo.sp_addlinkedserver
@server = N'LS_AsanaDSN' --Linked server name (this will be used in OPENQUERY sql)
, @srvproduct=N''
---- For MSSQL 2012,2014,2016 and 2019 use below (SQL Server Native Client 11.0)---
, @provider=N'SQLNCLI11'
---- For MSSQL 2022 or higher use below (Microsoft OLE DB Driver for SQL Server)---
--, @provider=N'MSOLEDBSQL'
, @datasrc=N'localhost,5000' --//Machine / Port where Gateway service is running
, @provstr=N'Network Library=DBMSSOCN;'
, @catalog=N'AsanaDSN' --Data source name you gave on Gateway service settings
--Attach gateway login with linked server
EXEC master.dbo.sp_addlinkedsrvlogin
@rmtsrvname=N'LS_AsanaDSN' --linked server name
, @useself=N'False'
, @locallogin=NULL
, @rmtuser=N'YOUR_GATEWAY_USER' --enter your Gateway user name
, @rmtpassword='YOUR_GATEWAY_PASSWORD' --enter your Gateway user's password
GO
--5. Enable RPC OUT (This is Optional - Only needed if you plan to use EXEC(...) AT YourLinkedServerName rather than OPENQUERY
EXEC sp_serveroption 'LS_AsanaDSN', 'rpc', true;
EXEC sp_serveroption 'LS_AsanaDSN', 'rpc out', true;
--Disable MSDTC - Below needed to support INSERT INTO from EXEC AT statement
EXEC sp_serveroption 'LS_AsanaDSN', 'remote proc transaction promotion', false;
--Increase query timeout if query is going to take longer than 10 mins (Default timeout is 600 seconds)
--EXEC sp_serveroption 'LS_AsanaDSN', 'query timeout', 1200;
GO
Here is the difference between OPENQUERY vs EXEC approaches:
Fetching Tables / Columns using metadata stored procs
ZappySys Data Gateway emulates certains system procs you might find in real SQL Server. You can call using below syntax using 4-Parts syntax
exec [linked-server-name].[gateway-datasource-name].[DATA].sp_tables
exec [linked-server-name].[gateway-datasource-name].[DATA].sp_columns_90 N'your-table-name'
Example:
//List all tables
exec [ls_AsanaDSN].[AsanaDSN].[DATA].sp_tables
//List all columns and its type for specified table
exec [ls_AsanaDSN].[AsanaDSN].[DATA].sp_columns_90 N'Account'
Known Issues
Let's explore some common problems that can occur when using OPENQUERY or Data Gateway connectivity.
SQL Native Client 11.0 not visible in the Providers dropdown (Linked Server Creation)
If you are following some screenshots / steps from our article it might say use SQL Native Client to create Linked Server to ZappySys Gateway but for some users they dont see that driver entry in the dropdown. This is due to the fact that Microsoft has deprecated SQL Native Client OLEDB Driver (SQLNCLI and SQLNCLI11) going forward after SQL 2022. So you need to use [Microsoft OLE DB Driver for SQL Server] instead (MSOLEDBSQL). Please follow all other instructions except the driver type selection, use new suggested driver instead if you dont see SQL Native Client.
Error: The data is invalid
There will be a time when, you may encounter unexpected errors like the ones listed below. These can include:
OLE DB provider "SQLNCLI11" for linked server "Zs_Csv" returned message "Deferred prepare could not be completed.".
OLE DB provider "SQLNCLI11" for linked server "Zs_Csv" returned message "Communication link failure".
Msg 13, Level 16, State 1, Line 0
Session Provider: The data is invalid.
Possible Cause:
There are few reasons for such error but below are two main reasons
-
If the query length exceeds 2000 characters, as shown below, you might encounter this error.
SELECT * FROM OPENQUERY(LS, '--some really long text more than 2000 chars--')
-
If a query contains multiple OPENQUERY statements for JOINs or UNIONs, as shown below, it might fail due to a MARS compatibility issue where the gateway doesn't support parallel queries on a single connection.
SELECT a.id, b.name from OPENQUERY(LS, 'select * from tbl1') a join OPENQUERY(LS, 'select * from tbl2') b on a.id=b.id
Possible Fix:
There are few ways to fix above error based on reason why you getting this error (i.e. Query Length issue OR JOIN/UNION in the same statement)
-
If your query has long SQL (more than 2000 chars ) then reduce SQL length using different techniques
-
If your query uses JOIN / UNION with multiple OPENQUERY in same SQL then use multiple Linked servers (one for each OPENQUERY clause) as below.
select a.id, b.name from OPENQUERY(LS_1, 'select * from tbl1') a join OPENQUERY(LS_2, 'select * from tbl2') b on a.id=b.id
Error: Unable to begin a distributed transaction (When INSERT + EXEC used)
If you try to use the EXEC statement to insert data into a table, as shown below, you might encounter the following error unless the MSDTC option is turned off.
INSERT INTO MyTable EXEC('select * from tbl') AT MyLinkedServer
"Protocol error in TDS stream"
The operation could not be performed because OLE DB provider "SQLNCLI11" for linked server "ls_Json2" was unable to begin a distributed transaction.
--OR--
The operation could not be performed because OLE DB provider "MSOLEDBSQL" for linked server "ls_Json" was unable to begin a distributed transaction.
Solution:
Method-1: Go to linked server properties | Server Options | Enable Promotion of Distributed Transaction | Change to false (Default is true)
Now your try your INSERT with EXEC AT and it should work
Method-2: Run the below command if you dont want to use UI
EXEC master.dbo.sp_serveroption @server=N'My_Linked_Server', @optname=N'remote proc transaction promotion', @optvalue=N'false'
Error: Cannot use OPENQUERY with JOIN / UNION
When you perform a JOIN or UNION ALL on the same Linked Server, it may fail to process sometimes because the Data Gateway doesn't support parallel query requests on the same connection. A workaround for that would be to create multiple linked servers for the same data source. Refer to the section above for the same workaround.
Error: Truncation errors due to data length mismatch
Many times, you may encounter truncation errors if a table column's length is less than the actual column size from the query column. To solve this issue, use the new version of Data Gateway and check the 'Use nvarchar(max) for string options' option found on the General Tab.
Performance Tips
Now, let's look at a few performance tips in this section.
Use INSERT INTO rather than SELECT INTO to avoid extra META request
We discussed some Pros and Cons of OPENQUERY vs EXEC (…) AT in previous section. One obvious advantage of EXEC (….) AT is it reduces number of requests to driver (It sends pass through query). With EXEC you cannot load data dynamically like SELECT INTO tmp FROM OPENQUERY. Table must exist before hand if you use EXEC.
INSERT INTO tmp_API_Report_Load(col1,col2)
EXEC('select col1,col2 from some_api_table') AT [API-LINKED-SERVER]
--OR--
INSERT INTO tmp_API_Report_Load(col1,col2)
select col1,col2 from OPENQUERY([API-LINKED-SERVER], 'select col1,col2 from some_api_table')
The advantage of this method is that your query speed will increase because the system only calls the API once when you use EXEC AT. In contrast, with OPENROWSET, the query needs to be called twice: once to obtain metadata and once to retrieve the data.
Use Cached Metadata if possible
By default, most SQL queries sent to the Data Gateway need to invoke two phases: first, to get metadata, and second, to fetch data. However, you can bypass the metadata API call by supplying static metadata. Use the META property in the WITH clause, as explained in
this article, to speed up your SQL queries.
Advanced topics
Create Custom Stored Procedure in ZappySys Driver
You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.
Steps to create Custom Stored Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
-
Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
-
Enter the desired Procedure name and click on OK:
-
Select the created Stored Procedure and write the your desired stored procedure and Save it and it will create the custom stored procedure in the ZappySys Driver:
Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
CREATE PROCEDURE [usp_get_orders]
@fromdate = '<<yyyy-MM-dd,FUN_TODAY>>'
AS
SELECT * FROM Orders where OrderDate >= '<@fromdate>';
-
That's it now go to Preview Tab and Execute your Stored Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:
Exec usp_get_orders '1996-01-01';
-
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC usp_get_orders @fromdate=''1996-07-30''')
-
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.
Create Custom Virtual Table in ZappySys Driver
ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.
If you're dealing with Microsoft Access and need to import data from an SQL query, it's important to note that Access doesn't allow direct import of SQL queries. Instead, you can create custom objects (Virtual Tables) to handle the import process.
Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.
-
Go to Custom Objects Tab and Click on Add button and Select Add Table:
-
Enter the desired Table name and click on OK:
-
And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.
-
Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here
SELECT
"ShipCountry",
"OrderID",
"CustomerID",
"EmployeeID",
"OrderDate",
"RequiredDate",
"ShippedDate",
"ShipVia",
"Freight",
"ShipName",
"ShipAddress",
"ShipCity",
"ShipRegion",
"ShipPostalCode"
FROM "Orders"
Where "ShipCountry"='USA'
-
That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:
SELECT * FROM "vt__usa_orders_only"
-
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')
-
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.
Actions supported by Asana Connector
Asana Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.
[
Read more...]
Parameter |
Description |
QueryBy |
Option |
Value |
project |
project |
tag |
tag |
section |
section |
user_task_list |
user_task_list |
assignee_and_workspace |
assignee_and_workspace |
|
Project Id |
The project to filter tasks on.
|
Workspace Id |
The workspace to filter tasks on. Note: If you specify workspace, you must also specify the assignee to filter on.
|
Assignee Id |
The assignee to filter tasks on. If searching for unassigned tasks, assignee.any = null can be specified. Note: If you specify assignee, you must also specify the workspace to filter on.
|
Section Id |
The section to filter tasks on.
|
Tag Id |
|
UserTaskListId |
|
Completed Since |
Only return tasks that are either incomplete or that have been completed since this time.
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Modified Since |
Only return tasks that have been modified since the given time. Note: A task is considered “modified” if any of its properties change, or associations between it and other objects are modified (e.g. a task being added to a project). A task is not considered modified just because another object it is associated with (e.g. a subtask) is modified. Actions that count as modifying the task include assigning, renaming, completing, and adding stories.
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Only enter TaskId if QueryBy=task else you may get error. [
Read more...]
Parameter |
Description |
QueryBy |
Option |
Value |
project |
project |
task |
task |
tag |
tag |
section |
section |
user_task_list |
user_task_list |
assignee_and_workspace |
assignee_and_workspace |
|
Parent Task Id |
The parent task id for which you would like to fetch all sub tasks.
|
Project Id |
The project to filter tasks on.
|
Workspace Id |
The workspace to filter tasks on. Note: If you specify workspace, you must also specify the assignee to filter on.
|
Assignee Id |
The assignee to filter tasks on. If searching for unassigned tasks, assignee.any = null can be specified. Note: If you specify assignee, you must also specify the workspace to filter on.
|
Section Id |
The section to filter tasks on.
|
Tag Id |
|
UserTaskListId |
|
Completed Since |
Only return tasks that are either incomplete or that have been completed since this time.
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Modified Since |
Only return tasks that have been modified since the given time. Note: A task is considered “modified” if any of its properties change, or associations between it and other objects are modified (e.g. a task being added to a project). A task is not considered modified just because another object it is associated with (e.g. a subtask) is modified. Actions that count as modifying the task include assigning, renaming, completing, and adding stories.
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Get tasks for all projects in a specified workspace (or default workspace). [
Read more...]
Parameter |
Description |
Fields |
Option |
Value |
actual_time_minutes |
actual_time_minutes |
subtasks |
subtasks |
approval_status |
approval_status |
assignee |
assignee |
assignee.name |
assignee.name |
assignee_section |
assignee_section |
assignee_section.name |
assignee_section.name |
assignee_status |
assignee_status |
completed |
completed |
completed_at |
completed_at |
completed_by |
completed_by |
completed_by.name |
completed_by.name |
created_at |
created_at |
created_by |
created_by |
created_by.name |
created_by.name |
custom_fields |
custom_fields |
custom_fields.asana_created_field |
custom_fields.asana_created_field |
custom_fields.created_by |
custom_fields.created_by |
custom_fields.created_by.name |
custom_fields.created_by.name |
custom_fields.currency_code |
custom_fields.currency_code |
custom_fields.custom_label |
custom_fields.custom_label |
custom_fields.custom_label_position |
custom_fields.custom_label_position |
custom_fields.date_value |
custom_fields.date_value |
custom_fields.date_value.date |
custom_fields.date_value.date |
custom_fields.date_value.date_time |
custom_fields.date_value.date_time |
custom_fields.description |
custom_fields.description |
custom_fields.display_value |
custom_fields.display_value |
custom_fields.enabled |
custom_fields.enabled |
custom_fields.enum_options |
custom_fields.enum_options |
custom_fields.enum_options.color |
custom_fields.enum_options.color |
custom_fields.enum_options.enabled |
custom_fields.enum_options.enabled |
custom_fields.enum_options.name |
custom_fields.enum_options.name |
custom_fields.enum_value |
custom_fields.enum_value |
custom_fields.enum_value.color |
custom_fields.enum_value.color |
custom_fields.enum_value.enabled |
custom_fields.enum_value.enabled |
custom_fields.enum_value.name |
custom_fields.enum_value.name |
custom_fields.format |
custom_fields.format |
custom_fields.has_notifications_enabled |
custom_fields.has_notifications_enabled |
custom_fields.id_prefix |
custom_fields.id_prefix |
custom_fields.is_formula_field |
custom_fields.is_formula_field |
custom_fields.is_global_to_workspace |
custom_fields.is_global_to_workspace |
custom_fields.is_value_read_only |
custom_fields.is_value_read_only |
custom_fields.multi_enum_values |
custom_fields.multi_enum_values |
custom_fields.multi_enum_values.color |
custom_fields.multi_enum_values.color |
custom_fields.multi_enum_values.enabled |
custom_fields.multi_enum_values.enabled |
custom_fields.multi_enum_values.name |
custom_fields.multi_enum_values.name |
custom_fields.name |
custom_fields.name |
custom_fields.number_value |
custom_fields.number_value |
custom_fields.people_value |
custom_fields.people_value |
custom_fields.people_value.name |
custom_fields.people_value.name |
custom_fields.precision |
custom_fields.precision |
custom_fields.representation_type |
custom_fields.representation_type |
custom_fields.resource_subtype |
custom_fields.resource_subtype |
custom_fields.text_value |
custom_fields.text_value |
custom_fields.type |
custom_fields.type |
dependencies |
dependencies |
dependents |
dependents |
due_at |
due_at |
due_on |
due_on |
external |
external |
external.data |
external.data |
followers |
followers |
followers.name |
followers.name |
hearted |
hearted |
hearts |
hearts |
hearts.user |
hearts.user |
hearts.user.name |
hearts.user.name |
html_notes |
html_notes |
is_rendered_as_separator |
is_rendered_as_separator |
liked |
liked |
likes |
likes |
likes.user |
likes.user |
likes.user.name |
likes.user.name |
memberships |
memberships |
memberships.project |
memberships.project |
memberships.project.name |
memberships.project.name |
memberships.section |
memberships.section |
memberships.section.name |
memberships.section.name |
modified_at |
modified_at |
name |
name |
notes |
notes |
num_hearts |
num_hearts |
num_likes |
num_likes |
num_subtasks |
num_subtasks |
parent |
parent |
parent.created_by |
parent.created_by |
parent.name |
parent.name |
parent.resource_subtype |
parent.resource_subtype |
permalink_url |
permalink_url |
projects |
projects |
projects.name |
projects.name |
resource_subtype |
resource_subtype |
start_at |
start_at |
start_on |
start_on |
tags |
tags |
tags.name |
tags.name |
workspace |
workspace |
workspace.name |
workspace.name |
|
Workspace Id |
The workspace to filter tasks on. Note: If you specify workspace.
|
Completed Since |
Only return tasks that are either incomplete or that have been completed since this time.
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Modified Since |
Only return tasks that have been modified since the given time. Note: A task is considered “modified” if any of its properties change, or associations between it and other objects are modified (e.g. a task being added to a project). A task is not considered modified just because another object it is associated with (e.g. a subtask) is modified. Actions that count as modifying the task include assigning, renaming, completing, and adding stories.
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Search Tasks (Advanced Filter)
Search tasks with in a specified workspace (or default workspace) using advanced server side filters. [
Read more...]
Parameter |
Description |
Fields |
Option |
Value |
actual_time_minutes |
actual_time_minutes |
subtasks |
subtasks |
approval_status |
approval_status |
assignee |
assignee |
assignee.name |
assignee.name |
assignee_section |
assignee_section |
assignee_section.name |
assignee_section.name |
assignee_status |
assignee_status |
completed |
completed |
completed_at |
completed_at |
completed_by |
completed_by |
completed_by.name |
completed_by.name |
created_at |
created_at |
created_by |
created_by |
created_by.name |
created_by.name |
custom_fields |
custom_fields |
custom_fields.asana_created_field |
custom_fields.asana_created_field |
custom_fields.created_by |
custom_fields.created_by |
custom_fields.created_by.name |
custom_fields.created_by.name |
custom_fields.currency_code |
custom_fields.currency_code |
custom_fields.custom_label |
custom_fields.custom_label |
custom_fields.custom_label_position |
custom_fields.custom_label_position |
custom_fields.date_value |
custom_fields.date_value |
custom_fields.date_value.date |
custom_fields.date_value.date |
custom_fields.date_value.date_time |
custom_fields.date_value.date_time |
custom_fields.description |
custom_fields.description |
custom_fields.display_value |
custom_fields.display_value |
custom_fields.enabled |
custom_fields.enabled |
custom_fields.enum_options |
custom_fields.enum_options |
custom_fields.enum_options.color |
custom_fields.enum_options.color |
custom_fields.enum_options.enabled |
custom_fields.enum_options.enabled |
custom_fields.enum_options.name |
custom_fields.enum_options.name |
custom_fields.enum_value |
custom_fields.enum_value |
custom_fields.enum_value.color |
custom_fields.enum_value.color |
custom_fields.enum_value.enabled |
custom_fields.enum_value.enabled |
custom_fields.enum_value.name |
custom_fields.enum_value.name |
custom_fields.format |
custom_fields.format |
custom_fields.has_notifications_enabled |
custom_fields.has_notifications_enabled |
custom_fields.id_prefix |
custom_fields.id_prefix |
custom_fields.is_formula_field |
custom_fields.is_formula_field |
custom_fields.is_global_to_workspace |
custom_fields.is_global_to_workspace |
custom_fields.is_value_read_only |
custom_fields.is_value_read_only |
custom_fields.multi_enum_values |
custom_fields.multi_enum_values |
custom_fields.multi_enum_values.color |
custom_fields.multi_enum_values.color |
custom_fields.multi_enum_values.enabled |
custom_fields.multi_enum_values.enabled |
custom_fields.multi_enum_values.name |
custom_fields.multi_enum_values.name |
custom_fields.name |
custom_fields.name |
custom_fields.number_value |
custom_fields.number_value |
custom_fields.people_value |
custom_fields.people_value |
custom_fields.people_value.name |
custom_fields.people_value.name |
custom_fields.precision |
custom_fields.precision |
custom_fields.representation_type |
custom_fields.representation_type |
custom_fields.resource_subtype |
custom_fields.resource_subtype |
custom_fields.text_value |
custom_fields.text_value |
custom_fields.type |
custom_fields.type |
dependencies |
dependencies |
dependents |
dependents |
due_at |
due_at |
due_on |
due_on |
external |
external |
external.data |
external.data |
followers |
followers |
followers.name |
followers.name |
hearted |
hearted |
hearts |
hearts |
hearts.user |
hearts.user |
hearts.user.name |
hearts.user.name |
html_notes |
html_notes |
is_rendered_as_separator |
is_rendered_as_separator |
liked |
liked |
likes |
likes |
likes.user |
likes.user |
likes.user.name |
likes.user.name |
memberships |
memberships |
memberships.project |
memberships.project |
memberships.project.name |
memberships.project.name |
memberships.section |
memberships.section |
memberships.section.name |
memberships.section.name |
modified_at |
modified_at |
name |
name |
notes |
notes |
num_hearts |
num_hearts |
num_likes |
num_likes |
num_subtasks |
num_subtasks |
parent |
parent |
parent.created_by |
parent.created_by |
parent.name |
parent.name |
parent.resource_subtype |
parent.resource_subtype |
permalink_url |
permalink_url |
projects |
projects |
projects.name |
projects.name |
resource_subtype |
resource_subtype |
start_at |
start_at |
start_on |
start_on |
tags |
tags |
tags.name |
tags.name |
workspace |
workspace |
workspace.name |
workspace.name |
|
Workspace Id |
The workspace to filter tasks on. Note: If you specify workspace.
|
Text |
Performs full-text search on both task name and description.
|
Projects (NOT) |
Comma-separated list of project IDs.
|
Projects (ALL) |
Comma-separated list of project IDs.
|
Projects (ANY) |
Comma-separated list of project IDs.
|
Sections (NOT) |
Comma-separated list of section IDs.
|
Sections (ALL) |
Comma-separated list of section IDs.
|
Sections (ANY) |
Comma-separated list of section IDs.
|
Tags (NOT) |
Comma-separated list of tag IDs.
|
Tags (ALL) |
Comma-separated list of tag IDs.
|
Tags (ANY) |
Comma-separated list of tag IDs.
|
Assigned By (NOT) |
Comma-separated list of user IDs.
|
Assigned By (ALL) |
Comma-separated list of user IDs.
|
Assigned By (ANY) |
Comma-separated list of user IDs.
|
Portfolios (ANY) |
Comma-separated list of portfolio IDs.
|
Teams (ANY) |
Comma-separated list of team IDs.
|
Due On |
ISO 8601 date string (e.g. 2025-12-31).
Option |
Value |
2023-12-31 |
2023-12-31 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Due On Before |
ISO 8601 date string (e.g. 2025-12-31).
Option |
Value |
2023-12-31 |
2023-12-31 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Due On After |
ISO 8601 date string (e.g. 2025-12-31).
Option |
Value |
2023-12-31 |
2023-12-31 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Due On (Null) |
Search for DueOn [null] value.
|
Start On |
ISO 8601 date string (e.g. 2025-12-31).
Option |
Value |
2023-12-31 |
2023-12-31 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Start On Before |
ISO 8601 date string (e.g. 2025-12-31).
Option |
Value |
2023-12-31 |
2023-12-31 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Start On After |
ISO 8601 date string (e.g. 2025-12-31).
Option |
Value |
2023-12-31 |
2023-12-31 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Start On (Null) |
Search for StartOn [null] value.
|
Created On |
ISO 8601 date string (e.g. 2025-12-31).
Option |
Value |
2023-12-31 |
2023-12-31 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Created On Before |
ISO 8601 date string (e.g. 2025-12-31).
Option |
Value |
2023-12-31 |
2023-12-31 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Created On After |
ISO 8601 date string (e.g. 2025-12-31).
Option |
Value |
2023-12-31 |
2023-12-31 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Created On (Null) |
Search for CreatedOn [null] value.
|
Modified On |
ISO 8601 date string (e.g. 2025-12-31).
Option |
Value |
2023-12-31 |
2023-12-31 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Modified On Before |
ISO 8601 date string (e.g. 2025-12-31).
Option |
Value |
2023-12-31 |
2023-12-31 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Modified On After |
ISO 8601 date string (e.g. 2025-12-31).
Option |
Value |
2023-12-31 |
2023-12-31 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Modified On (Null) |
Search for ModifiedOn [null] value.
|
Completed On |
ISO 8601 date string (e.g. 2025-12-31).
Option |
Value |
2023-12-31 |
2023-12-31 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Completed On Before |
ISO 8601 date string (e.g. 2025-12-31).
Option |
Value |
2023-12-31 |
2023-12-31 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Completed On After |
ISO 8601 date string (e.g. 2025-12-31).
Option |
Value |
2023-12-31 |
2023-12-31 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Completed On (Null) |
Search for CompletedOn [null] value.
|
Due At |
ISO 8601 date string (e.g. 2025-12-31T23:59:59).
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Due At Before |
ISO 8601 date string (e.g. 2025-12-31T23:59:59).
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Due At After |
ISO 8601 date string (e.g. 2025-12-31T23:59:59).
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Start At |
ISO 8601 date string (e.g. 2025-12-31T23:59:59).
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Start At Before |
ISO 8601 date string (e.g. 2025-12-31T23:59:59).
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Start At After |
ISO 8601 date string (e.g. 2025-12-31T23:59:59).
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Created At |
ISO 8601 date string (e.g. 2025-12-31T23:59:59).
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Created At Before |
ISO 8601 date string (e.g. 2025-12-31T23:59:59).
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Created At After |
ISO 8601 date string (e.g. 2025-12-31T23:59:59).
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Modified At |
ISO 8601 date string (e.g. 2025-12-31T23:59:59).
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Modified At Before |
ISO 8601 date string (e.g. 2025-12-31T23:59:59).
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Modified At After |
ISO 8601 date string (e.g. 2025-12-31T23:59:59).
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Completed At |
ISO 8601 date string (e.g. 2025-12-31T23:59:59).
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Completed At Before |
ISO 8601 date string (e.g. 2025-12-31T23:59:59).
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Completed At After |
ISO 8601 date string (e.g. 2025-12-31T23:59:59).
Option |
Value |
2023-12-31 |
2023-12-31 |
2023-12-31T00:00:00 |
2023-12-31T00:00:00 |
now |
now |
now-24h |
now-24h |
today |
today |
yesterday |
yesterday |
yearstart-10y |
yearstart-10y |
monthstart |
monthstart |
monthend |
monthend |
yearstart |
yearstart |
yearend |
yearend |
weekstart |
weekstart |
weekend |
weekend |
yearstart-1y |
yearstart-1y |
yearend-1y |
yearend-1y |
monthstart-1d |
monthstart-1d |
monthend+1d |
monthend+1d |
monthend+1d-1y |
monthend+1d-1y |
|
Is Blocked |
Option |
Value |
true |
true |
false |
false |
|
Is Blocking |
Option |
Value |
true |
true |
false |
false |
|
Is Subtask |
Option |
Value |
true |
true |
false |
false |
|
Has Attachment |
Option |
Value |
true |
true |
false |
false |
|
Completed |
Option |
Value |
true |
true |
false |
false |
|
Sort By |
Option |
Value |
due_date |
due_date |
created_at |
created_at |
completed_at |
completed_at |
modified_at |
modified_at |
likes |
likes |
|
Sort Ascending |
Option |
Value |
true |
true |
false |
false |
|
Returns records for all teams in the workspace visible to the authorized user. [
Read more...]
Parameter |
Description |
Workspace Id |
|
[
Read more...]
Parameter |
Description |
Workspace Id |
|
Project Id |
|
User Id |
|
Get Attachments (For Project refer to Key-Resources Upload only)
There are three possible parent values for this request: project, project_brief, and task. For a project, an attachment refers to a file uploaded to the [Key resources] section in the project Overview. For a project brief, an attachment refers to inline files in the project brief itself. For a task, an attachment refers to a file directly associated to that task. Note that within the Asana app, inline images in the task description do not appear in the index of image thumbnails nor as stories in the task. However, requests made to GET /attachments for a task will return all of the images in the task, including inline images. [
Read more...]
Parameter |
Description |
Parent Id (e.g. Id of Project, Task or ProjectBrief) |
Globally unique identifier for object to fetch statuses from. Must be a GID for a project, project_brief, or task.
|
Download a specific attachment by Id. [
Read more...]
Parameter |
Description |
Attachment ID |
The attachment Id for the attachment to get.
|
Fields |
Option |
Value |
name |
name |
resource_subtype |
resource_subtype |
connected_to_app |
connected_to_app |
created_at |
created_at |
download_url |
download_url |
host |
host |
parent |
parent |
parent.name |
parent.name |
parent.resource_subtype |
parent.resource_subtype |
permanent_url |
permanent_url |
size |
size |
view_url |
view_url |
|
Download Multiple Attachments
Download Multiple Attachments for a specified parent.There are three possible parent values for this request: project, project_brief, and task. For a project, an attachment refers to a file uploaded to the [Key resources] section in the project Overview. For a project brief, an attachment refers to inline files in the project brief itself. For a task, an attachment refers to a file directly associated to that task. Note that within the Asana app, inline images in the task description do not appear in the index of image thumbnails nor as stories in the task. However, requests made to GET /attachments for a task will return all of the images in the task, including inline images. [
Read more...]
Parameter |
Description |
Parent Id (e.g. Id of Project, Task or ProjectBrief) |
Globally unique identifier for object to fetch statuses from. Must be a GID for a project, project_brief, or task.
|
OverwriteFile |
Option |
Value |
True |
True |
False |
False |
|
SaveFolder |
Specify a disk folder path to save file(s) to
|
Fields |
Option |
Value |
name |
name |
resource_subtype |
resource_subtype |
connected_to_app |
connected_to_app |
created_at |
created_at |
download_url |
download_url |
host |
host |
parent |
parent |
parent.name |
parent.name |
parent.resource_subtype |
parent.resource_subtype |
permanent_url |
permanent_url |
size |
size |
view_url |
view_url |
|
[
Read more...]
Parameter |
Description |
Workspace Id |
|
Project Id |
|
Portfolio Id |
|
Team Id |
|
Is Workspace Level |
Option |
Value |
true |
true |
false |
false |
|
Time Periods (e.g. Id1,Id2) |
|
Get Workspace Custom Fields
Get Project Custom Fields
Get Portfolio Custom Fields
[
Read more...]
Parameter |
Description |
Project Id |
|
PortfolioId |
|
GoalId |
|
Member or Team Id (Use with Project OR Portfolio OR Goal) |
|
Get Time Tracking Entries
This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL. [
Read more...]
Parameter |
Description |
Url |
API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
|
Body |
Request Body content goes here
|
IsMultiPart |
Set this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value)
==== Raw Upload (Content-Type: application/octet-stream) =====
To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip )
==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) =====
To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored.
If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type.
See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored).
file1=@c:\data\Myfile1.txt
file2=@c:\data\Myfile2.json
file2.Content-Type=application/json
SomeField1=aaaaaaa
SomeField1.Content-Type=text/plain
SomeField2=12345
SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab
SomeFieldStartingWithAtSign=\@MyTwitterHandle
|
Filter |
Enter filter to extract array from response. Example: $.rows[*] --OR-- $.customers[*].orders[*]. Check your response document and find out hierarchy you like to extract
Option |
Value |
No filter |
|
Example1 |
$.store.books[*] |
Example2 (Sections Under Books) |
$.store.books[*].sections[*] |
Example3 (Equals) |
$.store.books[?(@author=='sam')] |
Example4 (Equals - Any Section) |
$..[?(@author=='sam')] |
Example5 (Not Equals - Any Section) |
$..[?(@author!='sam')] |
Example6 (Number less than) |
$.store.books[?(@.price<10)]
Example7 (Regular Expression - Contains Pattern)=$.store.books[?(@author=~ /sam|bob/ )] |
Example8 (Regular Expression - Does Not Contain Pattern) |
$.store.books[?(@author=~ /^((?!sam|bob).)*$/ )] |
Example9 (Regular Expression - Exact Pattern Match) |
$.store.books[?(@author=~ /^sam|bob$/ )] |
Example10 (Regular Expression - Starts With) |
$.store.books[?(@author=~ /^sam/ )] |
Example11 (Regular Expression - Ends With) |
$.store.books[?(@author=~ /sam$/ )] |
Example12 (Between) |
$.store.employees[?( @.hiredate>'2015-01-01' && @.hiredate<'2015-01-04' )] |
|
Headers |
Headers for Request. To enter multiple headers use double pipe or new line after each {header-name}:{value} pair
|
Generic Request (Bulk Write)
This is a generic endpoint for bulk write purpose. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL. [
Read more...]
Parameter |
Description |
Url |
API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
|
IsMultiPart |
Set this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value)
==== Raw Upload (Content-Type: application/octet-stream) =====
To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip )
==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) =====
To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored.
If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type.
See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored).
file1=@c:\data\Myfile1.txt
file2=@c:\data\Myfile2.json
file2.Content-Type=application/json
SomeField1=aaaaaaa
SomeField1.Content-Type=text/plain
SomeField2=12345
SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab
SomeFieldStartingWithAtSign=\@MyTwitterHandle
|
Filter |
Enter filter to extract array from response. Example: $.rows[*] --OR-- $.customers[*].orders[*]. Check your response document and find out hierarchy you like to extract
|
Headers |
Headers for Request. To enter multiple headers use double pipe (||) or new line after each {header-name}:{value} pair
|
Asana Connector Examples for SQL Server Connection
This page offers a collection of SQL examples designed for seamless integration with the ZappySys API ODBC Driver under ODBC Data Source (36/64) or ZappySys Data Gateway, enhancing your ability to connect and interact with Prebuilt Connectors effectively.
Read all workspaces
Read all projects
Read Tasks (default project) [Read more...]
Read all tasks (default project)
Read Tasks for a specific project [Read more...]
Read all tasks for a specified project
SELECT * FROM Tasks WITH (ProjectId='1200652735638082')
Read Sub Tasks - First Level (default project) [Read more...]
Read all first level sub tasks for default project. If you sub tasks for 3rd, 4th level deep then this wont capture.
Read Sub Tasks - First Level for specified project [Read more...]
Read all first level sub tasks for a specified project id. If you sub tasks for 3rd, 4th level deep then this wont capture.
SELECT * FROM SubTasks WITH (ProjectId='1200652735638082')
Read Sub Tasks for a specified parent task [Read more...]
SELECT * FROM SubTasks WITH(QueryBy='task', TaskId='1207150838176996')
Read Workspace Tasks (All Projects) [Read more...]
SELECT * FROM WorkspaceTasks
Search Tasks (Advanced Filters - Just like Asana Search UI) [Read more...]
--//search text in task title or description
SELECT * FROM search_tasks WITH(Text='Hotfix')
--//search text in all tasks from any projects listed below
SELECT * FROM search_tasks WITH(Text='Hotfix', ProjectsAny='1200652735638082,1206028542305053')
--//list all tasks from any projects listed below
SELECT * FROM search_tasks WITH(Text='Hotfix', ProjectsAny='1200652735638082,1206028542305053')
--//list all tasks due on specified date (same way you can use CreatedOn, CompletedOn ...)
SELECT * FROM search_tasks WITH(DueOn='2024-12-21')
--//list all tasks with due date after specified date (same way you can use CreatedOnAfter, CompletedOnAfter ...)
SELECT * FROM search_tasks WITH(DueOnAfter='2024-12-21')
SELECT * FROM search_tasks WITH(DueOnAfter='yearstart+1d')
--//list all tasks with due date after specified date (same way you can use CreatedOnBefore, CompletedOnBefore ...)
SELECT * FROM search_tasks WITH(DueOnBefore='2024-12-21')
SELECT * FROM search_tasks WITH(DueOnBefore='monthstart-5d')
--//list all tasks with due date after specified datetime (same way you can use CreatedAtBefore, CompletedAtBefore ...)
SELECT * FROM search_tasks WITH(DueAtBefore='2024-12-21T23:59:59')
SELECT * FROM search_tasks WITH(DueAtBefore='now-10h')
--//list all tasks with attachment
SELECT * FROM search_tasks WITH(HasAttachment='true')
Download Attachment to Local Disk [Read more...]
Download Attachment to Local Disk File.
SELECT * FROM download_attachment
WITH (
AttachmentId='1208216218258030'
, TargetFilePath='c:\temp\1208216218258030_AWS-refund-request.png'
, FileOverwriteMode=0 --0=AlwaysOverwrite, 1=FailIfExists, 2=SkipIfExists
)
Download Multiple Attachments to Local Disk [Read more...]
Download Multiple Attachments for a specified Parent (e.g. Task, Project, ProjectBrief) to Local Disk Folder. Saved file name syntax is {AttachmentId}_{FileName}.
SELECT * FROM download_attachments
WITH (
ParentId='1206673375982078' --Id of Task , Project or ProjectBrief
, SaveFolder='c:\temp'
, OverwriteFile=1
)
Read Portfolios for a specified Owner [Read more...]
Read Portfolios for a specified Owner (Default Workspace).
SELECT * FROM Portfolios WITH(OwnerId='1200442904128317')
Read Portfolios for a specified Owner and Workspace [Read more...]
Read Portfolios for a specified Owner Id and Workspace id.
SELECT * FROM Portfolios WITH(OwnerId='1200442904128317', WorkspaceId='1200442900140748')
Read Goals for a specified Project Id.
SELECT * FROM Goals WITH(Project='1206673375982078')
Read Goals for a specified Workspace Id.
SELECT * FROM Goals WITH(Workspace='1200442900140748')
Read Goals for a specified Team Id.
SELECT * FROM Goals WITH(Team='1200442900140748')
Read Memberships for a project [Read more...]
Read Memberships for a specific project.
SELECT * FROM Memberships WITH(ProjectId=1206673375982078)
Read Memberships for a project [Read more...]
Read Memberships for a specific project.
SELECT * FROM Memberships WITH(PortfolioId=1206673375982077)
Read Time Entries for a Task [Read more...]
Read Time Entries for a specific task.
SELECT * FROM TimeTrackingEntries WITH(TaskId=1207150837043133)
Conclusion
In this article we discussed how to connect to Asana in SQL Server and integrate data without any coding. Click here to Download Asana Connector for SQL Server and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).
Download Asana Connector for SQL Server
Documentation
More integrations
Other application integration scenarios for Asana
Other connectors for SQL Server
Download Asana Connector for SQL Server
Documentation
Common Searches:
How to connect Asana in SQL Server?
How to get Asana data in SQL Server?
How to read Asana data in SQL Server?
How to load Asana data in SQL Server?
How to import Asana data in SQL Server?
How to pull Asana data in SQL Server?
How to push data to Asana in SQL Server?
How to write data to Asana in SQL Server?
How to POST data to Asana in SQL Server?
Call Asana API in SQL Server
Consume Asana API in SQL Server
Asana SQL Server Automate
Asana SQL Server Integration
Integration Asana in SQL Server
Consume real-time Asana data in SQL Server
Consume real-time Asana API data in SQL Server
Asana ODBC Driver | ODBC Driver for Asana | ODBC Asana Driver | SSIS Asana Source | SSIS Asana Destination
Connect Asana in SQL Server
Load Asana in SQL Server
Load Asana data in SQL Server
Read Asana data in SQL Server
Asana API Call in SQL Server