tap-delighted

This is a Singer tap that produces JSON-formatted data following the Singer spec.

This tap:

• Pulls raw data from the delighted API.

• Extracts the following resources:

  • People

  • SurveyResponses

  • Metrics

  • Unsubscribes

  • Bounces

  • EmailAutopilot

  • SmsAutopilot

• Outputs the schema for each resource

• Incrementally pulls data based on the input state

Streams

people

• Primary keys: id
• Replication strategy: INCREMENTAL

survey_responses

• Primary keys: id
• Replication strategy: INCREMENTAL

metrics

• Primary keys: []
• Replication strategy: FULL_TABLE

unsubscribes

• Primary keys: person_id
• Replication strategy: INCREMENTAL

bounces

• Primary keys: person_id
• Replication strategy: INCREMENTAL

email_autopilot

• Primary keys: ["person_id", "next_survey_request_id"]
• Replication strategy: INCREMENTAL

sms_autopilot

• Primary keys: ["person_id", "next_survey_request_id"]
• Replication strategy: INCREMENTAL

Authentication

Quick Start

1. Install

   Clone this repository, and then install using setup.py. We recommend using a virtualenv:

   > virtualenv -p python3 venv
   > source venv/bin/activate
   > python setup.py install
   OR
   > cd .../tap-delighted
   > pip install -e .

2. Dependent libraries. The following dependent libraries were installed.

   > pip install singer-python
   > pip install target-stitch
   > pip install target-json
   

   • singer-tools
   • target-stitch

3. Create your tap's config.json file. The tap config file for this tap should include these entries:

   • api_key - The API key from your delighted account
   • start_date - The default value to use if no bookmark exists for an endpoint (rfc3339 date string)

   {
       "api_key": "your_api_key_here",
       "start_date": "2019-01-01T00:00:00Z"
   }

   Optionally, also create a state.json file. currently_syncing is an optional attribute used for identifying the last object to be synced in case the job is interrupted mid-stream. The next run would begin where the last job left off.

   {
       "currently_syncing": "dummy_stream1",
       "bookmarks": {
           "dummy_stream1": "2019-09-27T22:34:39.000000Z",
           "dummy_stream2": "2019-09-28T15:30:26.000000Z",
           "dummy_stream3": "2019-09-28T18:23:53Z"
       }
   }

4. Run the Tap in Discovery Mode This creates a catalog.json for selecting objects/fields to integrate:

   tap-delighted --config config.json --discover > catalog.json

   See the Singer docs on discovery mode here.

5. Run the Tap in Sync Mode (with catalog) and write out to state file

   For Sync mode:

   > tap-delighted --config tap_config.json --catalog catalog.json > state.json
   > tail -1 state.json > state.json.tmp && mv state.json.tmp state.json

   To load to json files to verify outputs:

   > tap-delighted --config tap_config.json --catalog catalog.json | target-json > state.json
   > tail -1 state.json > state.json.tmp && mv state.json.tmp state.json

   To pseudo-load to Stitch Import API with dry run:

   > tap-delighted --config tap_config.json --catalog catalog.json | target-stitch --config target_config.json --dry-run > state.json
   > tail -1 state.json > state.json.tmp && mv state.json.tmp state.json

6. Test the Tap While developing the delighted tap, the following utilities were run in accordance with Singer.io best practices: Pylint to improve code quality:

   > pylint tap_delighted -d missing-docstring -d logging-format-interpolation -d too-many-locals -d too-many-arguments

   Pylint test resulted in the following score:

   Your code has been rated at 9.67/10

   To check the tap and verify working:

   > tap_delighted --config tap_config.json --catalog catalog.json | singer-check-tap > state.json
   > tail -1 state.json > state.json.tmp && mv state.json.tmp state.json

   Unit Tests

   Unit tests may be run with the following.

   python -m pytest --verbose
   

   Note, you may need to install test dependencies.

   pip install -e .'[dev]'
   

---

Copyright © 2019 Stitch