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
  1. Crash Course of ImpulseSync
  2. Step 2: Jobs

Step 2a: Content manipulators

PreviousJob ConfigurationNextStep 2b: Content mapper

Last updated 1 year ago

overview of content manipulator.

Content manipulators allow us to change and manipulate content we have a wide variety of different content manipulators but we are able to change and manipulate content with our configuration, in this example we will be using the Regex content manipulator we have a wide variety of content manipulators but for this demo we will be using this one. This content manipulator in specific will search content or a string of words and replace it with whatever we fill the field in with.

Content manipulators can only be applied to jobs and aren't applied to endpoints themselves but we define the timing of when these changes should apply form a content manipulator. Each content manipulator has different set up that you can see here, for now were going to be walking through the concepts of setting one up and specifically in this case setting up a regex manipulator. Lets take a look at the Regex content manipulator we have a few fields from:

-fieldName: This is the field name variable that applies the regex to this is the field that impulse will serach for a correct match of the inputted regex string. This is a common value to fill in setting up a content manipulator and this uses the variable of the platform we are syncing content from. -regex: The string we add that impulseSync will use to find and replace content. -replace: This is what the searched regex string will be replaced with. -sourceContentType: Most content manipulators can be used on both source and destination part of a sync this means either the manipulation will apply when the content is picked up OR when the content is dropped off at the destination for best performance and consistency we recccomend using it when the content is read/picked up.

This content manipulator will search the string we put in under the "replace" field, and change the content so we can put in a simple string of what the variable is of our field content we want to have changed when its synced to the destination. For this lets have it apply on when the content is picked up so when the content is picked up by impulsesync it will apply this manipulation before syncing the content to the destination. To do this we simply need to add the field variable name that we want to manipulate, for this example in our content type we have a field called "title" so we will fill this field with title in order to change and replace it in the destination. Next we must add a regex that we want and we will add a string that needs to be searched which will be the value of our title field in this case "Technology and Architecture", Now we must add a value for the replace field this is what we will be replacing the value of the title field with, lets replace it with "Ins and Outs of ImpulseSync". This means its now all configured and ready to go if you have a been following these steps exactly it should look something like this:

The next thing to set up after adding a content manipulator is the Content Mapper.