update sources, add url

Author: markzegarelli

scripts/papi.js

@@ -276,25 +276,29 @@ const updateSources = async () => {
   sources.forEach(source => {
     let slug = slugify(source.name)
     let settings = source.options
-    let mainCategory = source.categories[0] ? source.categories[0].toLowerCase : ''
+    let mainCategory = source.categories[0] ? source.categories[0].toLowerCase() : ''
+
+    if (libraryCategories.includes(mainCategory)) {
+      url = `connections/sources/catalog/libraries/${mainCategory}/${slug}`
+    } else {
+      url = `connections/sources/catalog/cloud-apps/${slug}`
+    }  
 
     settings.sort((a, b) => {
       if(a.name < b.name) { return -1; }
       if(a.name > b.name) { return 1; }
       return 0;
     })
 
+    // console.log(slug, mainCategory)
 
-    if (libraryCategories.includes(mainCategory)) {
-      url = `connections/sources/catalog/libraries/${mainCategory}/${slug}`
-    } else {
-      url = `connections/sources/catalog/cloud-apps/${slug}`
-    }  
+
 
 
     let updatedSource = {
       display_name: source.name,
       slug,
+      url,
       description: source.description,
       logo: {
         url: source.logos.default
@@ -495,6 +499,6 @@ const updateWarehouses = async () => {
 
 }
 
-updateDestinations()
+//updateDestinations()
 updateSources()
 // updateWarehouses()

src/_data/catalog/destinations.yml

@@ -5246,6 +5246,67 @@ items:
     summary: accepts device-mode data only from Analytics.js.
     cmode_type: device-only
     case: '2'
+- display_name: Crisp
+  name: Crisp
+  slug: crisp
+  hidden: false
+  url: connections/destinations/catalog/crisp
+  previous_names:
+  - Crisp
+  website: 'https://crisp.chat'
+  status: PUBLIC
+  categories:
+  - CRM
+  - Customer Success
+  - Email Marketing
+  - Marketing Automation
+  logo:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/db6f4c77-470b-429c-b77a-77b1228ade63.svg
+  mark:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/45cad587-47d4-4ada-a09d-c730242af27e.svg
+  methods:
+    track: true
+    pageview: false
+    identify: true
+    group: false
+    alias: false
+  components:
+  - code: 'https://github.com/baptistejamin/analytics.js-integration-crisp'
+    type: browser
+  platforms:
+    browser: true
+    mobile: true
+    server: true
+  browserUnbundlingSupported: false
+  browserUnbundlingPublic: false
+  replay: false
+  settings:
+  - name: apiKey
+    type: string
+    defaultValue: ''
+    description: >-
+      The API key is autoset when linking Crisp with Segment. Click "Connect to
+      Segment" in the Crisp plugins section
+    required: true
+  - name: websiteId
+    type: string
+    defaultValue: ''
+    description: ''
+    required: true
+  connection_modes:
+    device:
+      web: true
+      mobile: false
+      server: false
+    cloud:
+      web: false
+      mobile: false
+      server: false
+    summary: accepts device-mode data only from Analytics.js.
+    cmode_type: device-only
+    case: '2'
 - display_name: Criteo App & Web Events
   name: Criteo App & Web Events
   slug: criteo-app-web-events
@@ -13046,81 +13107,6 @@ items:
       Cloud Mode or send track events from one of our server side libraries. Use
       these fields to map your Segment track event names to Marketo Custom
       Activities. We'll only send events that you specify.
-<<<<<<< HEAD
-=======
-    settings:
-    - name: marketoActivityId
-      display_name: Marketo Custom Activity ID
-      type: STRING
-      deprecated: false
-      required: true
-      string_validators:
-        regexp: '^[0-9]+$'
-      description: Enter the Marketo Custom Activity ID. This must be an Integer.
-      settings: []
-    - name: segmentProperty
-      display_name: Marketo Fields
-      type: MIXED
-      deprecated: false
-      required: false
-      description: Map your Segment properties to the Marketo Activity Fields
-      settings:
-      - name: marketoAttributeType
-        display_name: Marketo Field Type
-        type: SELECT
-        deprecated: false
-        required: true
-        select_validators:
-          select_options:
-          - string
-          - boolean
-          - number
-          - date
-        description: Enter the Marketo Field type.
-        settings: []
-      - name: primaryKey
-        display_name: Set as Primary Key
-        type: BOOLEAN
-        deprecated: false
-        required: false
-        description: Mark this property as the Primary field in Marketo.
-        settings: []
-      - name: segmentProperty
-        display_name: Segment Property Name
-        type: STRING
-        deprecated: false
-        required: true
-        string_validators:
-          regexp: ''
-        description: >-
-          Enter the Segment Property Name. This is case sensitive so make sure
-          the name matches exactly how you are passing it in your .track() call.
-        settings: []
-      - name: marketoAttributeName
-        display_name: Marketo Field Name
-        type: STRING
-        deprecated: false
-        required: true
-        string_validators:
-          regexp: ''
-        description: >-
-          Enter the Marketo Field name. Make sure to copy and paste the exact
-          API Name for your field as it appears in Marketo.
-        settings: []
-    - name: event
-      display_name: Segment Event Name
-      type: STRING
-      deprecated: false
-      required: true
-      string_validators:
-        regexp: ''
-      description: Enter the Segment Event Name.
-      settings: []
-  - name: traits
-    display_name: Marketo Custom Fields
-    type: MIXED
-    deprecated: false
->>>>>>> master
     required: false
   - name: privateKey
     type: string
@@ -17116,124 +17102,7 @@ items:
     description: >-
       Use these fields to map your Segment event names to Responsys Supplemental
       Tables. We'll only send events and properties that you specify.
-<<<<<<< HEAD
-    required: false
-=======
-    settings:
-    - name: columns
-      display_name: Columns
-      type: MIXED
-      deprecated: false
-      required: false
-      description: Map your Segment properties to Responsys Columns
-      settings:
-      - name: fieldName
-        display_name: Responsys Column Name
-        type: STRING
-        deprecated: false
-        required: true
-        string_validators:
-          regexp: ''
-        description: Enter the Responsys column name.
-        settings: []
-      - name: fieldType
-        display_name: Responsys Column Type
-        type: SELECT
-        deprecated: false
-        required: true
-        select_validators:
-          select_options:
-          - CHAR
-          - STR25
-          - STR100
-          - STR500
-          - STR4000
-          - Number
-          - INTEGER
-          - TIMESTAMP
-        description: Enter the Responsys column type.
-        settings: []
-      - name: primaryKey
-        display_name: Set as Primary Key
-        type: BOOLEAN
-        deprecated: false
-        required: false
-        description: Mark this property as a Primary Key in Responsys.
-        settings: []
-      - name: columns
-        display_name: Segment Property Name
-        type: STRING
-        deprecated: false
-        required: true
-        string_validators:
-          regexp: ''
-        description: Enter the Segment Property Name.
-        settings: []
-    - name: mapEmail
-      display_name: Map Email
-      type: BOOLEAN
-      deprecated: false
-      required: false
-      description: >-
-        Check this box if you want to automatically create and or map Segment's
-        `email` property (in `context.traits.email` or `properties.email`) as a
-        column in Responsys. Highly **recommended** if you are calling
-        `.identify()` with an `email` trait for anonymous users without
-        `userId`s.
-      settings: []
-    - name: mapUserId
-      display_name: Map Segment UserId
-      type: BOOLEAN
-      deprecated: false
-      required: false
-      description: >-
-        Check this box if you want to automatically create and or map Segment's
-        `userId` field as a column in Responsys. Highly **recommended** if you
-        want to connect records in your Profile Lists/Extension Tables with
-        records in this Supplemental Table.
-      settings: []
-    - name: folderName
-      display_name: Responsys Folder Name
-      type: STRING
-      deprecated: false
-      required: true
-      string_validators:
-        regexp: ''
-      description: >-
-        Optional. Enter a Responsys Folder Name where this Supplemental exists
-        or where you'd like one to be created. If this input is left blank, we
-        will fallback on the default Folder Name you've provided at the top
-        level settings.
-      settings: []
-    - name: suppName
-      display_name: Responsys Supplemental Table Name
-      type: STRING
-      deprecated: false
-      required: true
-      string_validators:
-        regexp: ''
-      description: Enter a Responsys Supplemental Table Name.
-      settings: []
-    - name: event
-      display_name: Segment Event Name
-      type: STRING
-      deprecated: false
-      required: true
-      string_validators:
-        regexp: ''
-      description: Enter the Segment Event Name.
-      settings: []
-    - name: useSegmentMsgId
-      display_name: Use Segment Message ID
-      type: BOOLEAN
-      deprecated: false
-      required: false
-      description: >-
-        Use Segment's `messageId` as one of the four Primary Keys to easily
-        ensure that you do not overwrite historical records in your Supplemental
-        Tables.
-      settings: []
->>>>>>> master
+    required: false
   - name: folderName
     type: string
     defaultValue: ''