Quick start guide

Out-of-office.email – Quick Start Guide – Rest API Guide

 

1. Sign up here for an account here (link to Memberstack sign up form on our website) and verify your email

2. After verifying your email, check the inbox for your API key (token). You will have 100 free credits to test parse emails without purchasing a paid plan.

3. See our Python example below for how to parse your email texts through the API.

import requests

# Define your API endpoint and authorization token
API_URL = “https://o3-api.azurewebsites.net/email/parse”
AUTH_TOKEN = “Bearer eyJhbGciOi…” # Replace with your valid token

email_text = “Hi! I have resigned, please contact my colleague.”

# Prepare the headers and payload for the API call
headers = {
“accept”: “application/json”,
“Authorization”: AUTH_TOKEN,
“Content-Type”: “application/json”
}
payload = {“email_text”: email_text}

# Make the API call
response = requests.post(API_URL, headers=headers, json=payload)

#Print result
print(response.json())

 

Out-of-office.email – How To Get Started – Zapier Guide

 

1. Sign up here for an account here (link to Memberstack sign up form on our website) and verify your email

2. After verifying your email, check the inbox for your API key (token). You will have 100 free credits to test parse emails without purchasing a paid plan.

3. Get invited to our Out-of-office Zapier App. You should automatically have access no later than 24 hours after first signing up.

Please contact customer support if you after 24 hours still do not have access.

4. Have your reply-to inbox ready in either Outlook or Gmail

a. This is the reply-to inbox for your email communication. This should usually be a “noreply” address. Example: noreply@example.com.

b. If you have trouble setting up your noreply inbox, please consult with us through our support channel.

5. Build your Zap

Gmail or Outlook as input (noreply inbox listener) -> Update any CRM/Database available in Zapier. https://zapier.com/apps/categories/crm?sort=popularity

Plug and play actions for routing different scenarios to correct CRM/Database action.

 

Action Example

add_new_contact: “Contact me at my new email: john.smith@example.com”

update_contact: “My email is now jane.doe@example.com”

replace_contact: “Please contact Robert Brown going forward”

add_alternate_contact: “While I’m away, contact Mary Johnson”

add_role_email: “Email registrator@example.net for inquiries”

remove_contact: “This email is no longer in use”

pause_communication: “I’m on leave until June 17th”

resend_email: “Please resend your message to robert.jones@example.com”

forward_future_emails: “In the future, contact emily.davis@example.net”