Yes. OASIS supports Canva design imports into the asset library, including source tracking, brand ownership, file validation, alt-text review, approvals, and rendition preparation for supported social channels.

Adobe Express is not currently listed as a native OASIS integration. Teams can manage finished creative assets in the asset library and route them through campaign, review, and publishing workflows.

The current public model covers Meta/Facebook/Instagram, LinkedIn, YouTube, TikTok, X, Bluesky, WhatsApp Business, Pinterest, Reddit, RSS/blogs, and forums. Support varies by provider: some are ready with setup, some are planned, and RSS/blog/forum sources are read-only.

OASIS models Instagram through the Meta provider path for professional Instagram accounts connected to Facebook Pages. Production use still depends on customer-owned Meta app configuration, required permissions, and any applicable provider review.

Threads is listed as planned. The current support boundary directs teams to the Meta page for Facebook and Instagram while Threads API behavior is verified.

Asana is not currently listed as a native integration. Campaign planning, task ownership, approvals, and audit trails are handled inside OASIS.

Yes. X is included in the public provider model with setup-dependent support for account connection, discovery, metrics, content reads, mentions, publishing, media upload, polling, and read-only ad data.

Salesforce is not currently listed as a native public integration. CRM-specific connector work should be scoped separately during implementation.

Wrike is not currently listed as a native integration. OASIS includes its own campaign planning, approvals, assignment, and governance workflows.

HubSpot is not currently listed as a native public integration. Marketing or CRM connector requirements should be reviewed as custom implementation scope.

Yes. LinkedIn is included as a ready-with-setup provider for organization pages, with support for account connection, publishing, media upload, content reads, metrics, replies, polling, mentions read, and read-only ad data where permitted.

Yes. OASIS supports Google Drive design and asset imports so teams can bring approved Drive files into governed folders, preserve source metadata, validate ownership, and route assets through review before publishing.

Yes. Instagram is supported through the Meta integration for professional Instagram accounts connected to Facebook Pages, including publishing, media upload, content reads, metrics, mentions, inbox reads, replies, moderation, and webhook ingestion where scopes and provider policy allow.

Slack is not currently listed as a native public integration. Team coordination, assignment, approval, and audit activity currently live inside OASIS.

Yes. Facebook is supported through the Meta integration, including Pages, publishing, media upload, content reads, metrics, inbox reads, mentions, engagement replies, moderation, webhooks, and read-only ad data where configured.

Facebook Shops is not currently documented as a native OASIS capability. The Meta integration focuses on social publishing, engagement, metrics, account health, and related governance workflows.

Google My Business is not currently listed in the public provider model. Current Google-family social support is represented through YouTube.

Bitly is not currently listed as a native integration. Link strategy and tracked campaign reporting can be handled through implementation-specific workflows if required.

Outlook is not currently listed as a native integration. OASIS handles operational queues, approvals, and notifications inside the platform unless a mail workflow is scoped separately.

Dropbox is not currently listed as a native public integration. Assets can be imported into OASIS and governed through the asset library and approval flows.

Shopify is not currently listed as a native integration. OASIS is focused on governed social operations rather than ecommerce catalog or storefront administration.

Google Analytics is not currently listed as a native integration. OASIS includes analytics and reporting for supported social providers, campaigns, paid activity, operations, and exports.

Yes. Reddit is supported for OAuth account connection, subreddit moderator accounts, governed text or link publishing, content reads, inbox and mention polling, replies, and approve or remove moderation actions where the connected account has permission.

Glassdoor is not currently listed as a native integration. Listening or reputation-monitoring needs for unsupported sources should be scoped through read-only collection or custom integration review.

Tripadvisor is not currently listed as a native integration. Review-source monitoring can be evaluated separately if it is part of a buyer requirement.

Monday.com is not currently listed as a native integration. OASIS includes internal planning, assignment, approval, and governance workflows for communications teams.

Pinterest is listed as planned. The current public model includes Pinterest in the integration directory, but not as a ready live provider.

Yes. YouTube is ready with setup for channel connection, video publishing and upload, native scheduling where available, content reads, metrics, comment replies, and polling.

Yes. TikTok is available with setup for business or creator accounts, video publishing and upload, profile and video reads, metrics, and polling where required scopes are available.

Zendesk is not currently listed as a native integration. OASIS includes its own unified inbox, saved replies, case management, assignment, escalation, and audit workflows.

Feedly is not currently listed as a native integration. RSS and blogs are represented as read-only sources in the public provider model.