Back to source plugin

Export from Bitly to Neo4j

CloudQuery is an open-source data integration platform that allows you to export data from any source to any destination.

The CloudQuery Bitly plugin allows you to sync data from Bitly to any destination, including Neo4j. It takes only minutes to get started.

Bitly
bitly
Official

Bitly

This plugin is in preview.

Sync Bitly links stats to a destination of your choice.

Publisher

cloudquery

Repositorygithub.com
Latest version

v1.1.0

Type

Source

Platforms
Date Published

Neo4j
neo4j
Official

Neo4j

This destination plugin lets you sync data from a CloudQuery source to a Neo4j database

Publisher

cloudquery

Repositorygithub.com
Latest version

v5.2.4

Type

Destination

Platforms
Date Published

MacOS Setup

Step 1. Install CloudQuery

brew install cloudquery/tap/cloudquery

Step 2. Log in to CloudQuery CLI

cloudquery login

Step 3. Configure Bitly source plugin

You can find more information about the configuration in the plugin documentation

kind: source
spec:
  name: "bitly"
  registry: "docker"
  path: "docker.cloudquery.io/cloudquery/source-bitly:v1.0.0"
  tables: ['*']
  destinations: ["sqlite"]
  spec:
    group_id: ${BITLY_GROUP_ID}     # mandatory
    api_token: ${BITLY_API_TOKEN}   # mandatory
    extract_utm: true               # optional. If set, extracts utm_tags from the long_url into separate columns
    # optional. unit to use to query last 1 {unit} of clicks by a country. Default: month. Values: hour, day, week, month.
    countries_summary_unit: "month" 
    # optional. unit to use to query last 1 {unit} of clicks by a referrer. Default: month. Values: hour, day, week, month.
    referrers_summary_unit: "month" 
    #optional: get data only for the links on the list 
    only: 
      - bit.ly/1234567
    # optional, includes only links created after the specified date. Supported formats:
    # - "YYYY-MM-DD"
    # - "-<number> <unit>" where number is integer and unit is "day", "week"
    created_after: "-1 day"

Step 4. Configure Neo4j destination plugin

You can find more information about the configuration in the plugin documentation

kind: destination
spec:
  name: "neo4j"
  path: "cloudquery/neo4j"
  registry: "cloudquery"
  version: "v5.2.4"
  # Learn more about the configuration options at https://cql.ink/neo4j_destination
  spec:
    connection_string: "${NEO4J_CONNECTION_STRING}"
    username: "${NEO4J_USERNAME}"
    password: "${NEO4J_PASSWORD}"
    # Optional parameters:
    # batch_size: 1000 # 1K entries
    # batch_size_bytes: 4194304 # 4 MiB

Step 5. Run Sync

cloudquery sync bitly.yml neo4j.yml

© 2024 CloudQuery, Inc. All rights reserved.