Skip to main content
Connect an Airship project once and Gradial can draft content templates, send notifications, manage audiences, and orchestrate scheduled sends across email, SMS, mobile push, web push, in-app, and Message Center — from a single flow.

​
What You Can Do

Content templates

Draft and update templates for any Airship channel: email, SMS, open channel, app (mobile push), web push, and Message Center. Preview rendered templates inline before sending.

Sending and scheduling

Send notifications immediately or schedule for a future time. View, update, or cancel existing schedules. Target named users, channels, segments, static lists, or audience expressions.

Audience management

Inspect and update named users and individual channels. Manage static lists and read existing segments. Look up which channels a user is reachable on before drafting a send.

Pipelines

View and manage Airship pipelines — event-triggered automations.

​
Prerequisites

  • Admin access to your Airship project to create credentials
  • Your Airship project’s regional API host (North America or Europe)
  • A Gradial organization Administrator role to complete setup

​
How to Connect

1

Get your authentication details from Airship

Airship supports three auth methods. Choose the one your security team prefers:OAuth Client Credentials (recommended)
  1. Sign in to Airship as a project admin and open OAuth Clients in your project settings.
  2. Create a dedicated client for Gradial, scoped to the operations the team needs (content templates, schedules, audiences, sends).
  3. Copy the App Key, Client ID, and Client Secret.
  4. Note your region (NA or EU).
App Key + Master Secret
  1. Open your Airship project’s Settings → APIs & Integrations.
  2. Copy the App Key and Master Secret.
The master secret has broad project access. Use this only when OAuth isn’t available, and rotate the secret on a regular cadence.
Base64 Credential Token If you already mint a Base64-encoded appKey:masterSecret token elsewhere in your tooling, paste it into the API-key-header dialog with the prefix Basic.
2

Add the integration in Gradial

  1. In Gradial, go to Settings → Integrations.
  2. Find Airship and click + Add.
  3. Fill in the connection details:
  1. Click Save. Gradial validates the credentials and region before the integration goes live.
3

Assign to an Environment

  1. Go to Settings → Environments and select the Gradial Environment where Airship should be available.
  2. Add the Airship integration to that Environment.
  3. Repeat for any additional Environments.

​
How It Fits Into Broader Workflows

Example — Author a multi-channel campaign:
  1. Ask Gradial to draft an email template for the campaign — subject, preheader, and body copy.
  2. Have Gradial draft a matching mobile push template and a web push template.
  3. Preview all three inline in the thread to QA the creative.
  4. Schedule each send for the same launch time, targeting the right segment or static list.
  5. Open the Airship artifact for each template to monitor in the Airship dashboard.

​
Good to Know

  • Region awareness: NA and EU Airship projects sit on different hostnames. The connection dialog auto-switches the API base URL when the region changes.
  • Sends never auto-retry: writes (sending a notification, creating a schedule, mutating audiences) intentionally do not retry on failure. A failed send is reported back and stops — the agent never silently double-sends.
  • Inline previews are sanitized: the preview proxy strips remote fonts, inline scripts, and unsafe CSS. It preserves inline data URIs and inline blobs so legitimate creative still previews correctly.
  • OAuth credential rotation: when rotating Airship OAuth credentials, Gradial preserves project-level config across the rotation. The old cached token can serve requests until its natural expiry (up to ~60 minutes), so plan for that window for security-motivated rotations.

​
Support

Contact your Gradial onboarding lead or email [email protected] for help with setup.