Slack Integration

Connect InboxIssue to Slack to run spam tests directly from your workspace and receive results in channels.

Setting Up Slack

1. Connect Your Workspace

1. Go to Settings > Integrations in InboxIssue
2. Click Add to Slack
3. Authorize the InboxIssue app in your Slack workspace
4. Select the channel for notifications

2. Required Permissions

InboxIssue requests these Slack permissions:

Using the /inboxissue Command

The /inboxissue command creates a new spam test directly from Slack.

Basic Usage

/inboxissue

Creates a test with all provider types (consumer, business, protected).

Filter by Provider Type

/inboxissue consumer

Creates a test with only consumer providers (Gmail, Yahoo, etc.).

Available filters:

• consumer - Gmail, Yahoo, AOL, Outlook.com, iCloud
• business - Office 365, Google Workspace
• protected - Mimecast, Proofpoint, Barracuda

Response

After running the command, InboxIssue responds with:

✅ Spam Test Created!

Test ID: ABC123
Tracking Key: inboxissue-12345-2024-01-15-inboxissue

Send your test email to:
test1@gmail.com, test2@yahoo.com, test3@outlook.com, ...

💡 Include the tracking key somewhere in your email body or subject.
🔔 Results will be posted here automatically when emails arrive.

Receiving Results

When test emails arrive at InboxIssue mailboxes, results are automatically posted to the channel:

Result Format

📊 Test Results for "Slack Test - Jan 15, 2024 10:30 AM"

Summary:
• Inbox: 8 (80%)
• Spam: 2 (20%)
• Missing: 0

View full results: [View Test]

Result Details

Click "View Test" to see:

• Per-provider delivery status
• Authentication results (SPF, DKIM, DMARC)
• Spam scores (Microsoft SCL/BCL)
• Full header analysis

Quick Test with .eml Files

The /quicktest command allows you to test an existing email file.

Usage

1. Run /quicktest in Slack
2. Select your SMTP account when prompted
3. Share a .eml file in the channel
4. InboxIssue sends the email to test addresses
5. Results are posted automatically

Supported File Types

Aborting a Command

To cancel a pending /quicktest:

/abort

This cancels the file upload wait.

Troubleshooting

"Please connect InboxIssue to Slack first"

Cause: Your Slack workspace isn't connected to InboxIssue.

Solution: Go to Settings > Integrations in InboxIssue and click "Add to Slack".

"No active email providers available"

Cause: No healthy email providers are available for testing.

Solution: Wait a few minutes and try again, or contact support.

"Failed to setup email monitoring"

Cause: Temporary issue with email monitoring setup.

Solution: Try the command again. If it persists, contact support.

Results Not Appearing

Cause: Emails may not have arrived yet.

Solution:

1. Verify you sent to all provided addresses
2. Check that the tracking key is included
3. Wait up to 15 minutes for results
4. Check your sending server for bounce messages

Best Practices

1. Use Dedicated Channels

Create a dedicated channel (e.g., #deliverability-tests) for spam test results.

2. Include Context

When running tests, add context in the channel:

Testing the new newsletter template...
/inboxissue

3. Review Results Promptly

Results are posted as they arrive. Review promptly to catch issues.

4. Integrate with Webhooks

Combine Slack tests with Webhooks for automated workflows.

Related

• Spam Tests - Full test documentation
• Webhooks - Automated notifications
• Test Examples - Real-world scenarios