ImpulseSync™ User Manual
HomePricingContact Us
  • Introduction
    • What is Impulse?
  • Crash Course of ImpulseSync
    • Overview Of ImpulseSync
    • Step 1: Endpoints
      • Endpoint Configuration
    • Step 2: Jobs
      • Job Configuration
      • Step 2a: Content manipulators
      • Step 2b: Content mapper
    • Step 3: Syncing
  • Getting Started
    • Core Concepts
    • Creating Endpoints
    • Creating Jobs
    • Starting a Transaction
    • Transaction Reports
    • Automating Jobs with Pipelines
    • Scripting Post Sync
    • Scheduling Jobs and Pipelines
    • Dashboard
    • Managing Jobs/Pipelines
    • Content Mapper
      • Aligning Mismatched Content
      • Connector Matrix
      • Locked Fields
      • Content Aligner
      • Aligning Content Challenges
  • Reports
    • Reports Screen
    • Debug Report
    • Messages
  • Connectors
    • Common Job Options
    • All Connectors List
    • Source Connectors
      • Contentful
      • Contentstack
      • dotCMS
      • Drupal v7
      • Drupal v9
      • GitHub
      • GraphQL
      • MS Teams
      • SCP
      • Snapshot
      • Strapi v3
      • Strapi v4
    • Destination Connectors
      • Contentful
      • Contentstack
      • dotCMS
      • SCP
      • Strapi v3
      • Strapi v4
  • Content Manipulators
    • Common Manipulator Options
    • Add Replace Field
    • AI(Artificial intelligence)
    • Change ID Manipulator
    • CSV Store Manipulator
    • Dynamic Job Store Manipulator
    • File to Text
    • Folder Manipulator
    • Get and Set Field
    • Language
    • Liquid Field
      • Liquid On the Quick
      • Basics
        • Impulse Values
        • Impulse Variables
        • Operators
        • Truthy and falsy
        • Types
        • Whitespace control
      • Tags
        • Control flow
        • Impulse Content Objects
        • Iteration
        • Utility
        • Variable
      • Filters
        • abs
        • append
        • capitalize
        • ceil
        • compact
        • concat
        • date
        • date_str
        • default
        • divided_by
        • downcase
        • escape
        • escape_once
        • first
        • floor
        • getStoredValue
        • htmlQuery
        • htmlReplace
        • idMap
        • join
        • jq
        • json
        • last
        • lstrip
        • map
        • minus
        • modulo
        • newline_to_br
        • plus
        • prepend
        • remove
        • remove_first
        • replace
        • replace_first
        • reverse
        • round
        • rstrip
        • section
        • sections
        • size
        • slice
        • sort
        • sort_natural
        • split
        • str_to_date
        • strip
        • strip_html
        • strip_newlines
        • times
        • truncate
        • truncatewords
        • type
        • uniq
        • upcase
        • utl_decode
        • url_encode
      • Liquid Playground
    • Markdown
    • Regex
    • Relationship
    • Store Field
    • Tidy
  • Time Machine
    • Snapshot
    • Viewing Snapshots
    • Delivery from Snapshots
  • Cookbook Recipes
    • Adding Fields
    • Aligning Content between Endpoints
    • Avoid overriding Fields
    • Avoid syncing Content Types
    • Combing Fields
    • Default Field Value
    • File (.doc) to Structured Content
    • File (.docx) to Structured Content - Expanded
    • HTML to Structured Content
    • Language (Locale) mismatch between endpoints
    • Paths/IDs Changed
    • Reference to Value
    • Single Content Type to Multiple
    • Splitting Content with Reference
    • Syncing Content with Languages
    • Text Select to Boolean
    • Text to Reference
    • Text to Reference - liquid
    • Two Sources to One Destination
    • Changing a folder path
    • Combining data between content types
    • Converting HTML Sections
    • JSON object to reference
    • Use CSV to convert values
    • Storing fields with Store field motator
  • Troubleshooting
    • What to do if I run into a Job Problem
    • Troubleshooting via UI
    • Submitting a ticket
  • Using Impulse Headlessly
    • Getting Started with cURL
      • Creating Endpoints
      • Creating Jobs
      • Starting a Transaction
      • Transaction Reports
      • Automating Jobs with Pipelines
      • Scheduling Jobs and Pipelines
      • Aligning Mismatched Content
      • Scripting Post Sync
  • Organization Tier Restrictions
  • Content Storage Options
Powered by GitBook
On this page
  • Specifics
  • Permissions
  • Registering ImpulseSync as an app
  • Endpoint Config
  • Connector queries for all files
  • Unsupported
  • Adapter Properties
  • Job Options
  • folder job option
  • Motation Object Support
  1. Connectors
  2. Source Connectors

MS Teams

PreviousGraphQLNextSCP

Last updated 1 year ago

The source MS Teams connector allows files and folders to be picked up from One Drive/Sharepoint and transformed into motation.

Specifics

The source MS Teams connector uses API to pick up the files and folders from One Drive/Sharepoint. You will need to register an single tennant application with the appropriate permissions to use this connector.

Permissions

Registering ImpulseSync as an app

You will need to register ImpulseSync as an application in . Register ImpulseSync as a single tennant.

Once it's registered you will have a tennant ID and a client ID. You will also need a.

Finally, ImpulseSync requires the appropriate permissions. It must be able to read the files for a drive in a site. This can be granted by granting the Files.Read.All permission.

Adding Files.Read.All permission

Click "Add a permission". Then select Microsoft Graph.

Select "Application permissions". Then type files.read.all into the search bar.

Then select the Files.Read.All permission and click "add permissions" at the bottom.

Finally, grant admin consent for the permission.

Endpoint Config

When saving an endpoint for a MS Teams repository via REST instead of the UI you must use the following key:value pairs in the payload.

  • contentRepo:ms-teams

  • contentRepoVersion:latest

Connector queries for all files

Because this connector uses the MS Graph API to pickup files, there are some restrictions inherited from the API.

Unsupported

Passing in a select param is unsupported.

Passing in an expand param is unsupported.

Passing in an order by param is unsupported.

Adapter Properties

Property
Purpose

clientId

The client ID for the registered ImpulseSync application in the MS identify platform.

clientSecret

The client secret for the registered ImpulseSync application in the MS identify platform.

tenantId

The tenant ID for the registered ImpulseSync application in the MS identify platform.

driveId

The drive ID to pick up files from.

siteId (optional)

The site ID the drive lives at to pick up files from. (default: no site id)

rateLimitPerSecond (optional)

The rate limit requests should be sent to the MS Graph API. (default: 10)

Job Options

Name
Description
Data Type
Required
Default Value

folder

The relative folder path from root of a drive to pick up files from.

Text

true

No Default Value

query

Text

false

No Default Value

folder job option

The folder job option is the relative folder path from the root of the drive ID.

Motation Object Support

Object
Supported

Category

No

Definition

Yes

Domain

No

Folder

Yes

Language

No

Relationship

No

Tag

No

One of these restrictions is the need to manually filter files based on a time stamp. The does not allow for a query to be made for files which sorts or filters by time stamp. This means the connector must query through all files in a folder on pickup. This can cause picking up files to take longer than expected for a transaction that is picking up files from a very large folder.

Anything unsupported by the MS Graph API is also unsupported by this connector. i.e., the sorting param only works with .

to be added to the API request to pick up files.

MS Graph API
name and url fields
MS Graph query parameters
MS Graph
Microsoft identity platform
client secret