Hello Joe,

I had been looking at potentially having to do this as well but realised I didn't need to do it.  Content is sync'd to graph on a near real time basis when the content is published through the front end, however most queries will be running with caching for performance purposes.

If you want to programmatically index content into graph, you could use the IContentIndexer which is part of the Optimizely.ContentGraph.Cms.Core namespace.  This has index methods that take either a single or a collection of content references.

Here is the interface for IContentIndexer

public interface IContentIndexer
{
    ContentIndexingScope? IndexingScope { get; }
    Task<Response> IndexAsync(ContentReference contentReference, bool throughEventHub = true, CancellationToken cancellationToken = default(CancellationToken));
    Task<IEnumerable<Response>> IndexToNewDeploymentAsync(IEnumerable<ContentReference> contentReferences, bool throughEventHub = true, CancellationToken cancellationToken = default(CancellationToken));
    Task<IEnumerable<Response>> IndexAsync(IEnumerable<ContentReference> contentReferences, bool throughEventHub = true, CancellationToken cancellationToken = default(CancellationToken));
    Task<Response> DeleteAsync(DeleteItemModel deleteItem);
    Task<Response> DeleteAsync(IEnumerable<DeleteItemModel> deleteItems, CancellationToken cancellationToken = default(CancellationToken));
    Task<Response> DeleteAsync(IEnumerable<DeleteByPathModel> deleteItems, CancellationToken cancellationToken = default(CancellationToken));
    Task<Response> DeleteAsync(DeleteByPathModel deleteItem);
    Task BufferedIndexAsync(ContentReference contentReference, CancellationToken cancellationToken = default(CancellationToken));
    Task BufferedIndexAsync(IEnumerable<ContentReference> contentReferences, CancellationToken cancellationToken = default(CancellationToken));
}

Thank you for the response Mark. I will take a look at that interface, and see what I can figure out. 

One thing I forgot to mention, is that the content in question is coming in from a DAM provider, and the way it was implemented uses stored procedures to make the updates, so there are not any content events, like publish, that are triggered. Hopefully this will give me what I need though.