We make data feeds so simple, you can run them from your phone.
Turn HR records, files, and API responses into ready-to-run onboarding feeds for your identity providers. Map the fields, catch data problems, preview account changes, and submit approved records in bulk. Millions of records. Multiple sources. One manageable process.
Millions of records. Multiple providers. One simple workflow.
Stop turning every onboarding feed into a separate manual process. Bring the records together, define the rules once, and give your team a clear way to review, run, and follow the results.
Use PeopleSoft, Oracle Fusion, Workday, and other workforce sources to prepare identity accounts. Set the source date window, map employee attributes, and check whether a person already has an account before deciding what to create or update.
Reduce the repeated work between HR data and account creation.
Upload a file, discover its columns, and turn them into destination attributes. Reuse transformation rules, identify duplicates and missing values, and select the eligible records to submit. Keep an outcome for each record instead of losing track in spreadsheets.
Give one-time and repeat file imports the same controls.
Connect Banner, business workflows, and custom sources through REST APIs or an approved integration layer. Configure the request and authentication, test the response, preview records, and save the source for use in your onboarding projects.
Bring your existing source into a consistent onboarding workflow.
Manage feeds for employees, contractors, students, and other onboarding populations across identity providers. Keep each project’s matching rules, mapping, and schedule clear. Use bulk submission within provider limits and track the records that succeeded or need attention.
Scale the record count without multiplying manual checks.
Source connections and destination capabilities are configured for your deployment. Synx focuses on getting onboarding data into the right account attributes with a reviewable, repeatable process.
People data rarely lives in one place. A hire may begin in an HR system, a contractor in a spreadsheet, and a profile change in a business workflow. Synx gives administrators a consistent way to turn those inputs into controlled account changes.
Make every feed manageable.
Bring in records from CSV, PeopleSoft, Oracle Fusion, Workday, Banner, and other systems through REST APIs or integration workflows. Connect HR, payroll, ERP, student information, and database-backed applications through the access method that fits your environment.
Test the connection and inspect returned records before saving. Set the URL, method, headers, parameters, body, authentication, and location of the record array in the response.
Choose the stable identifier that represents the same person in both systems. Map discovered source columns to destination attributes, translate values, and define reusable rules for missing or differently formatted data.
Save feeds as projects so different populations and business processes have their own configuration, mappings, and operating schedules.
The workflow is organized around identity records and attributes, rather than a single vendor’s vocabulary. The destination connection translates approved changes into the operations your identity platform supports.
We assess API access, schemas, matching rules, supported operations, and service limits for your chosen platform. We define the connection path for each source and destination, including the required API capabilities and supported bulk operations.
A feed should answer three simple questions: what data came in, what will happen to it, and what actually succeeded?
Start with the population you need.
Compare against saved destination data.
Let background processing do the work.
Reviewing a feed does not create accounts. Submission is a separate action, with supported onboarding notification choices shown before confirmation.
Move from connection setup to a scheduled operation through a clear sequence. Each stage gives you a chance to inspect the data and resolve issues before they affect accounts.
Test a data source and preview its records. Synx discovers the available fields so you can build mappings from the actual response. CSV sources use the uploaded column headings. API sources can use date parameters to limit the population returned.
Select an employee ID or another stable identifier, connect fields, and configure transformations. A source field can feed more than one destination attribute. Review suggestions, adapt them to your organization, and save the mapping.
Compare the selected source dataset with the saved destination snapshot. See how many records would create an account, update mapped attributes, remain unchanged, or need attention. Inspect current and proposed values before applying changes.
Search and filter the review, select one person, a subset, or all eligible records, then inspect the confirmation summary. Choose the supported onboarding notification option before submitting. Records with unresolved identity conflicts stay out of the import.
Processing continues in the background. Open Requests to follow progress, inspect provider responses, and review record outcomes. Confirmed successes, failures, unprocessed records, and unconfirmed outcomes are distinguished so a partial result is not mistaken for a completed run.
Once the feed is ready, set its schedule and source lookback period. Refresh source and destination data on their own schedules, and use saved snapshots for comparisons. The snapshot view brings recent activity, scheduled runs, health, and exceptions together.
A source saying “A” and a destination expecting “true” should not require a spreadsheet cleanup every time. Synx makes attribute transformations part of the saved feed.
Turn source status codes into destination values. For example, map an active employment code to an enabled account, with explicit handling for other statuses.
Build a display name from first and last name, or assemble a formatted address. Map the same source field to multiple destination attributes when the business process requires it.
Define a fallback derived from a stable, unique username instead of giving everyone the same placeholder email. Validate the resulting values and resolve duplicates before submission.
Trim leading and trailing spaces from final values so invisible whitespace does not generate unnecessary changes. Preserve meaningful internal spacing and review the transformed result before saving.
Scale should not make everyday operations harder. MYID Synx brings your feeds, identity providers, and data sources into one responsive workspace you can use from your desktop, tablet, or phone.
Check your snapshot, see what needs attention, inspect proposed changes, and choose the records to include. The same review and confirmation process travels with you.
Submit a feed and let background processing do the work. Follow progress, counts, errors, and request details without keeping the page open. Come back when you need to check an outcome or resolve an exception.
Manage large record populations across feeds and identity providers while bulk processing and provider-aware batching handle execution. Millions of records can be managed across your environment; individual requests still respect each provider’s limits.
Automation is useful when the operating team can understand it. Synx pairs execution with the controls and evidence needed to manage real feeds.
Define when source refreshes, destination refreshes, and feed runs occur. Use a rolling lookback such as the last few days or months to calculate source date ranges. Manual refresh controls support an immediate check; an existing refresh is reused rather than duplicated.
See the source, destination, initiator, manual or automatic trigger, duration, status, and outcomes. Drill into processing steps and provider messages. Review progress and estimated remaining time while work runs, including from a mobile device.
Use supported bulk and asynchronous job APIs, with batches sized to provider record and payload limits. Follow the provider job through processing and retrieve its results. Connector behavior, concurrency, and rate limits are part of the integration design.
Separate missing values, invalid emails, duplicate identifiers, and conflicting matches into understandable reasons. Open a reason’s record list, inspect the matching accounts, and export the details for correction. Resolve the identity relationship rather than guessing which account to change.
Review unsuccessful and unsubmitted records for retry as a new request, keeping the original history. Inspect unconfirmed outcomes before repeating them. Cancellation stops pending work and requests provider cancellation where supported; changes already applied are not automatically rolled back.
Keep request history, processing activity, connection checks, configuration changes, and refresh audit copies available for investigation. Export tables to CSV for review. Refresh copies follow a 14-day retention window, while provider jobs and reports can be cleaned up after required results are retrieved.
Bring in the relevant hire population, transform HR fields into account attributes, check for existing identities, and review the proposed creations. Submit eligible records with an explicit notification choice and follow the result.
Keep mapped names, departments, titles, contact details, and other supported attributes aligned with an authoritative source. A comparison separates real changes from accounts whose mapped values already match.
Use an approved CSV file or an API from a partner process when a population does not originate in the main HR system. Give that feed its own project, mappings, identity matching, and operating cadence.
Preview a population before introducing it to a destination. Begin with a selected subset, resolve conflicts, and use recorded outcomes to decide when the feed is ready for a wider run.
Prepare a defined intake from Banner, an API, or a file. Keep matching and transformation rules with the project, inspect the proposed accounts, and process the eligible population in bulk.
Give identity administrators, HR integration owners, and support teams a common record of what was requested and what happened. A searchable history and exportable exceptions make handoffs easier to follow.
No single provider defines the product’s workflow. Synx is designed to connect source records to your chosen identity destination through an appropriate integration. Availability of specific connectors and actions is confirmed during scoping; a provider-neutral approach does not mean every platform works without configuration or connector development.
Yes, the source can be exposed through a configured REST endpoint, a workflow, an integration service, or a CSV export. For databases and private systems, agree an approved access method that returns the needed records. The connection must meet the feed’s authentication, response-format, completeness, and performance requirements.
A comparison prepares proposed actions against the saved source and destination data. It lets you inspect records and select eligible changes before submitting an import. Refreshing a snapshot and applying account changes are separate operations.
Connection and processing errors appear in the request history. Saved snapshots remain useful for inspection, with their refresh times visible. A timeout is not proof that a submitted change failed: unconfirmed results need investigation before retry. Schedule health checks and operational review around the reliability requirements of your feed.
No. A missing row could simply be outside a date range or part of an incomplete source response. Disabling requires an explicit mapped status and a supported, configured destination operation. This prevents a partial onboarding dataset from being treated as a list of accounts to disable.
Yes. Save feeds as projects and reuse saved data-source definitions. Keep the population, mapping, source window, and schedule clear for each project. Plan attribute ownership where feeds overlap so separate processes do not compete to update the same field.
Bring one source, one intended destination, a sample record, and the account changes you want to automate. We review identifiers, transformations, API capabilities, notification requirements, and exception handling, then build a scoped feed you can test before scheduling.
Show us the systems, the people data, and the account work you want to simplify. We’ll help define a feed that fits your environment.