The tap-wrike extractor pulls data from Wrike that can then be sent to a destination using a loader.
Alternate Implementations
Getting Started
Prerequisites
If you haven't already, follow the initial steps of the Getting Started guide:
Installation and configuration
- 
                      Add the tap-wrike extractor to your
                      project using
                      
:meltano add - 
                        Configure the tap-wrike
                        settings using
                        
:meltano config - 
                        Test that extractor settings are valid using
                        
:meltano config 
meltano add extractor tap-wrikemeltano config tap-wrike set --interactivemeltano config tap-wrike testNext steps
Follow the remaining steps of the Getting Started guide:
If you run into any issues, learn how to get help.
Capabilities
      The current capabilities for
      tap-wrike
      may have been automatically set when originally added to the Hub. Please review the
      capabilities when using this extractor. If you find they are out of date, please
      consider updating them by making a pull request to the YAML file that defines the
      capabilities for this extractor.
    
This plugin has the following capabilities:
- catalog
 - discover
 - state
 
      You can
      override these capabilities or specify additional ones
      in your meltano.yml by adding the capabilities key.
    
Settings
Authorization
See the Wrike developer authorization docs for more details on setting up an app and getting credentials.
      The
      tap-wrike settings that are known to Meltano are documented below. To quickly
      find the setting you're looking for, click on any setting name from the list:
    
      You can also list these settings using
      
      with the meltano configlist
      subcommand:
    
meltano config tap-wrike list
      You can
      override these settings or specify additional ones
      in your meltano.yml by adding the settings key.
    
Please consider adding any settings you have defined locally to this definition on MeltanoHub by making a pull request to the YAML file that defines the settings for this plugin.
Client ID (client_id)
- 
          Environment variable:
          
TAP_WRIKE_CLIENT_ID 
Your Wrike client ID, if using OAuth2 credentials.
Configure this setting directly using the following Meltano command:
meltano config tap-wrike set client_id [value]Client Secret (client_secret)
- 
          Environment variable:
          
TAP_WRIKE_CLIENT_SECRET 
Your Wrike client secret, if using OAuth2 credentials.
Configure this setting directly using the following Meltano command:
meltano config tap-wrike set client_secret [value]Refresh Token (refresh_token)
- 
          Environment variable:
          
TAP_WRIKE_REFRESH_TOKEN 
Your Wrike refresh token, if using OAuth2 credentials.
Configure this setting directly using the following Meltano command:
meltano config tap-wrike set refresh_token [value]Token (token)
- 
          Environment variable:
          
TAP_WRIKE_TOKEN 
Your Wrike permanent token, if using a permanent access token auth flow.
Configure this setting directly using the following Meltano command:
meltano config tap-wrike set token [value]Something missing?
This page is generated from a YAML file that you can contribute changes to.
Edit it on GitHub!Looking for help?
#plugins-general
    channel.
  

